[Pulp-list] Failed upgrade pulp 2.10 -> 2.12

[Michael Hrivnak]

We found the user object that was in an bad state and corrected it. The
workaround is documented here:

https://pulp.plan.io/issues/2591#note-14

Thanks, Kodiak, for helping us gather more info about the bug!

Michael

On Sat, Mar 18, 2017 at 4:21 PM, Kodiak Firesmith <kfiresmith at gmail.com>
wrote:

> <3 Michael, <3 Brian - I'm on #pulp right now w/ Michael, but I'm also in
> the DB and removed a single user account I found with no defined roles [],
> and tried running the pulp-manage-db to no avail.  I'll work on a redacted
> paste.
>
> On Sat, Mar 18, 2017 at 4:18 PM, Brian Bouterse <bbouters at redhat.com>
> wrote:
>
>> It sounds like issue 2591 was not environmental for the original
>> reporter. Can you show the output of the current users table with the
>> password redacted? You can do that with:  db.users.find().pretty()  in a
>> mongo shell connected to the Pulp db. Could you also paste that same output
>> from your db backup (also redacted), so we can compare? In fact, I will
>> reopen 2591 and untriage it, but can you post both of this output on the
>> issue? From that output we could determine what the right mongo command to
>> run is for the workaround.
>>
>> Also are there many usernames in use in your environment?
>>
>>
>>
>> On Sat, Mar 18, 2017 at 3:49 PM, Kodiak Firesmith <kfiresmith at gmail.com>
>> wrote:
>>
>>> Hi Folks,
>>> After having no problem upgrading beta, I took on a weekend upgrade of
>>> prod and just my luck, can't upgrade the DB.
>>>
>>> Sadly, I'm no programmer and certainly not a MongoDB whiz so I'm a bit
>>> dead in the water after hitting this:
>>>
>>> https://paste.fedoraproject.org/paste/PADDDdL112VnEiJOVJqell
>>> 5M1UNdIGYhyRLivL9gydE=
>>>
>>> My recovery plan was to basically just run a 'yum history undo ##', but
>>> I discovered I can't roll back to 2.10-1 easily because the packages no
>>> longer seem to exist on the internet - I should have checked and mirrored
>>> them before taking on the upgrade, shame on me and an opportunity to
>>> improve my future process to be sure.
>>>
>>> Anyhow, google brings me exactly one hit for the pasted error above:
>>> https://pulp.plan.io/issues/2591
>>>
>>> ...But I'm not so sure on messing around with the Pulp production DB,
>>> despite having backups it still makes me wary.
>>>
>>> Anyone have any advice?
>>>
>>> Thanks much!
>>>  - Kodiak
>>>
>>> _______________________________________________
>>> Pulp-list mailing list
>>> Pulp-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-list
>>>
>>
>>
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20170318/61a3c8e8/attachment.htm>