[Openstack-operators] [puppet] [cinder] - some snapshots are there, but they are hidden in the snapshot-list
Saverio Proto
zioproto at gmail.com
Thu Mar 24 07:52:32 UTC 2016
Hello there,
because I need to tune osapi_max_limit I wrote this puppet patch
https://review.openstack.org/#/c/296931/
but I am very bad at coding :) please review :)
Saverio
2016-03-23 11:17 GMT+01:00 Saverio Proto <zioproto at gmail.com>:
> It looks like not all snapshots are listed because I am hitting the
> osapi_max_limit
>
> # The maximum number of items that a collection resource
> # returns in a single response (integer value)
> #osapi_max_limit=1000
>
> Saverio
>
>
> 2016-03-23 9:29 GMT+01:00 Saverio Proto <zioproto at gmail.com>:
>> Hello,
>>
>> I upgraded to Kilo and I see the very same bug.
>>
>> What is the right way to fill a bug to Cinder, is it here ?
>> https://bugs.launchpad.net/cinder
>>
>> Will it be considered if the Bug is in Kilo ?
>>
>> thank you
>>
>> Saverio
>>
>>
>> 2016-03-16 13:42 GMT+01:00 Saverio Proto <zioproto at gmail.com>:
>>> Hello there,
>>>
>>> I could not believe my eyes today.
>>> We are talking about Cinder in Juno.
>>> So we have a use case where we have to be sure we do snapshots
>>> everyday, so we have a script that tries to do the snapshot in this
>>> way:
>>>
>>> while [ `/usr/bin/cinder snapshot-list | grep $DISPLAY_NAME | wc -l` -eq 0 ]; do
>>> /usr/bin/cinder snapshot-create --force True --display-name
>>> $DISPLAY_NAME $VOLUME_ID >> $LOG_FILE 2>&1
>>> sleep 5
>>> done
>>>
>>> Looking over the log file we noticed that every snapshot required 3 or
>>> 4 tries to go through. Digging into the logs I found that I have some
>>> snapshots that are valid, but they do not appear in the snapshot-list.
>>>
>>> This is what I mean:
>>>
>>> $ cinder snapshot-list | grep d0a750fd-37dd-43ee-87d8-aacbcacc5dc4
>>> $ cinder snapshot-show d0a750fd-37dd-43ee-87d8-aacbcacc5dc4
>>> +--------------------------------------------+--------------------------------------+
>>> | Property | Value
>>> |
>>> +--------------------------------------------+--------------------------------------+
>>> | created_at |
>>> 2016-03-15T23:30:21.000000 |
>>> | display_description | None
>>> |
>>> | display_name | backup--130-20160316-00:30 |
>>> | id |
>>> d0a750fd-37dd-43ee-87d8-aacbcacc5dc4 |
>>> | metadata | {}
>>> |
>>> | os-extended-snapshot-attributes:progress | 100%
>>> |
>>> | os-extended-snapshot-attributes:project_id |
>>> bdf747f88fee4b5a9faca3da7c26754c |
>>> | size | 2048
>>> |
>>> | status | available
>>> |
>>> | volume_id |
>>> 34d9a7a5-0383-4e59-8293-e9f9d4989490 |
>>> +--------------------------------------------+--------------------------------------+
>>> $
>>>
>>> Very same thing with the latest openstack client
>>>
>>> macsp:~ proto$ openstack snapshot list | grep
>>> d0a750fd-37dd-43ee-87d8-aacbcacc5dc4
>>> macsp:~ proto$ openstack snapshot show d0a750fd-37dd-43ee-87d8-aacbcacc5dc4
>>> +--------------------------------------------+--------------------------------------+
>>> | Field | Value
>>> |
>>> +--------------------------------------------+--------------------------------------+
>>> | created_at |
>>> 2016-03-15T23:30:21.000000 |
>>> | description | None
>>> |
>>> | id |
>>> d0a750fd-37dd-43ee-87d8-aacbcacc5dc4 |
>>> | name | backup--130-20160316-00:30 |
>>> | os-extended-snapshot-attributes:progress | 100%
>>> |
>>> | os-extended-snapshot-attributes:project_id |
>>> bdf747f88fee4b5a9faca3da7c26754c |
>>> | properties |
>>> |
>>> | size | 2048
>>> |
>>> | status | available
>>> |
>>> | volume_id |
>>> 34d9a7a5-0383-4e59-8293-e9f9d4989490 |
>>> +--------------------------------------------+--------------------------------------+
>>>
>>> I checked the entry in the mysql database for this snapshots, they
>>> look exactly identical to other entries where the snapshot appear.
>>>
>>> Is this a old Juno bug ?
>>>
>>> thank you
>>>
>>> Saverio
More information about the OpenStack-operators
mailing list