fuel-dev team mailing list archive
-
fuel-dev team
-
Mailing list archive
-
Message #01480
Re: Fuel master node upgrade - bugs statuses
>> and if this issue will happen really often, we will increase the
priority and will fix it asap
Good. Sounds like we are on the same page. We should be fine as long as it
doesn't happen very often. There will be time in 6.0 to clean it up,
upgrade Docker, and get rid of the issues.
Also, basic math rules apply. If it fails with 10% probability, you get 90%
(1.0-0.1) success on the first attempt. While the probability of failing
two times in a row is only .1*.1 = 1%, so the success rate after the second
attempt should be quite high.
Either way, I hope it won't be as frequent as 10%.
Thanks,
Roman
On Tue, Aug 26, 2014 at 4:14 AM, Evgeniy L <eli@xxxxxxxxxxxx> wrote:
> Hi Roman,
>
> >> https://bugs.launchpad.net/fuel/+bug/1359725 (Docker dies during the
> upgrade)
>
> I saw the problem 2 times, including the one which is in the ticket. I ran
> upgrade
> more than hundred of times and haven't seen the issue.
>
> >> https://bugs.launchpad.net/fuel/+bug/1357357 (Upgrades, sometimes
> docker
> allocates the same IPs for different containers)
>
> Personally I haven't seen it, and believe that the probability to get
> the error is very low, lets say 2 to 100, the issue which I see
> really often is [1] ports duplication and it has the same symptoms.
> We were able to debug it today and Matthew submit patches.
>
> And if this issue will happen really often, we will increase the
> priority and will fix it asap, but for now we have really annoying
> random problems like [1].
>
> [1] https://bugs.launchpad.net/fuel/+bug/1349287
>
>
>
> On Tue, Aug 26, 2014 at 4:18 AM, Roman Alekseenkov <
> ralekseenkov@xxxxxxxxxxxx> wrote:
>
>> There's been a parallel thread, but still. I have a question regarding
>> Docker-related issues:
>> - https://bugs.launchpad.net/fuel/+bug/1359725 (Docker dies during the
>> upgrade)
>> - https://bugs.launchpad.net/fuel/+bug/1357357 (Upgrades, sometimes
>> docker allocates the same IPs for different containers)
>>
>> How consistently we can reproduce these problems?
>>
>> I would like to understand how bad the issue is. I.e.
>> - what are the chances that upgrade will fail on the 1st attempt (because
>> of either of those issues)
>> - what are the chances that upgrade will fail on the 2nd attempt (i.e.
>> user will have to run upgrade.sh more than two times)
>>
>> There's been a number of decisions already impacting UX in a negative way
>> (confusing versioning in OpenStack patching, large size of the upgrade
>> tarball, issues with containers) and we just can't afford going down the
>> slippery slope.
>>
>> Thanks,
>> Roman
>>
>>
>> On Mon, Aug 25, 2014 at 6:52 AM, Evgeniy L <eli@xxxxxxxxxxxx> wrote:
>>
>>> Hi, here you can find a list of problems which we
>>> have for the current release
>>>
>>> *Problem with keystone container during the upgrade*
>>> https://bugs.launchpad.net/fuel/+bug/1353574
>>> It happens often on my environment, there is a patch from
>>> Matthew to fix the problem
>>> https://review.openstack.org/#/c/116613/
>>> <https://review.openstack.org/#/c/116613/1>
>>>
>>> *Docker dies during the upgrade*
>>> https://bugs.launchpad.net/fuel/+bug/1359725
>>> It happens not often, but I saw it 2 times I
>>> wrote the instruction how to work around it, also
>>> it affects 5.0.1 upgrade tar ball, we should add
>>> it to known issues list
>>> https://bugs.launchpad.net/fuel/+bug/1359725/comments/5
>>>
>>> *Build iptables 1.4.11 for centos*
>>> https://bugs.launchpad.net/fuel/+bug/1359096
>>> Waiting for mos-linux team, it should help to
>>> solve problems with duplicated iptables rules
>>> in some cases
>>>
>>> *5.1 upgrade script failed with UpgradeVerificationError: *
>>> *Failed to run services ['integration_postgres_nailgun_nginx', *
>>>
>>> *'integration_nginx_nailgun'] *
>>> https://bugs.launchpad.net/fuel/+bug/1349287
>>> It was reopened, we are trying to reproduce it to get
>>> the environment with the problem
>>>
>>> *Upgrades, sometimes docker allocates the same IPs*
>>>
>>> *for different containers*
>>> https://bugs.launchpad.net/fuel/+bug/1357357
>>> Decided to move to 6.0, because it can be fixed only
>>> by patched docker, it's very risky to upgrade docker,
>>> decided to postpone.
>>> Details are here
>>> https://www.mail-archive.com/fuel-dev@xxxxxxxxxxxxxxxxxxx/msg01328.html
>>>
>>>
>>> Thanks
>>>
>>> --
>>> Mailing list: https://launchpad.net/~fuel-dev
>>> Post to : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>> More help : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>
References