On Fri, Jul 1, 2016 at 3:24 PM, Dylan Baars <[email protected]> wrote:
> Morning Eric, > > no worries! Glad I could help (and of course thanks for helping me!). If I > apply the change to my existing 3.0.1 install which failed, do I just run > the upgrade command again? Or should I revert my VM to 2.4 and do the > upgrade again? > To keep going with your current 3.0 will require some migration reverting and while it's do-able, if you can rollback to your 2.4 and go fresh I'd recommend that. Eric > > Dylan > > On Sat, Jul 2, 2016 at 4:22 AM, Eric D Helms <[email protected]> wrote: > >> Thanks a ton Dylan! In the end the fix was a simple one [1] but had large >> ramifications that I could not have solved without your database! >> >> If you'd like to patch your 3.0.1 with the change and do your upgrade, >> feel free. I tested it on your data set with success. I will be working to >> push out a 3.0.2 that includes the fix officially as soon as it is merged >> if you'd rather wait for an official release of it. >> >> Again, thanks a ton for sharing your data to help resolve this for >> everyone, >> Eric >> >> >> [1] https://github.com/Katello/katello/pull/6162 >> >> On Fri, Jul 1, 2016 at 7:16 AM, Dylan Baars <[email protected]> wrote: >> >>> Hey Eric, >>> >>> I just sent a Google Drive share to you at your redhat address, if you >>> didn't get it you should be able to pick up the files from >>> >>> >>> https://drive.google.com/folderview?id=0BzOJej1vQpyfZnBKcndzY0RBaGs&usp=sharing >>> >>> Enjoy ;-) >>> Dylan >>> >>> On Fri, Jul 1, 2016 at 10:58 PM, Eric D Helms <[email protected]> >>> wrote: >>> >>>> Yea, a dump of the 'foreman' and 'candlepin' database as l will need >>>> both from the 2.4 box preupgrade. The easiest option is to use [1] and >>>> email me ([email protected]) the file names that you upload. If you'd >>>> prefer a different method please let me know and we'll figure something >>>> out. >>>> >>>> [1] https://access.redhat.com/solutions/2112 >>>> On Jul 1, 2016 6:37 AM, "Dylan Baars" <[email protected]> wrote: >>>> >>>>> Happy to do either! I guess a DB backup is easier for you to work >>>>> with, let me know how to get that to you (you're after the Postgres >>>>> db I take it?) >>>>> >>>>> Dylan >>>>> >>>>> On Friday, 1 July 2016, Eric D Helms <[email protected]> wrote: >>>>> >>>>>> Dylan, >>>>>> >>>>>> You've hit an error that I spent the past two days debugging for >>>>>> another user but have not been able to replicate locally. Couple of >>>>>> questions for you: >>>>>> >>>>>> 1) do you have a backup of your 2.4 before upgrading? >>>>>> 2) If yes, would you be able to privately share backups of your >>>>>> database with me from 2.4? If you are unable to share it out, would you >>>>>> be >>>>>> willing to help by doing some live debugging on IRC or some other means? >>>>>> On Jul 1, 2016 1:15 AM, "Dylan Baars" <[email protected]> wrote: >>>>>> >>>>>>> I had a further error, final output below >>>>>>> >>>>>>> Upgrade Step: restart_services... >>>>>>> Upgrade Step: db_seed... >>>>>>> Upgrade Step: import_package_groups (this may take a while) ... >>>>>>> Upgrade Step: import_rpms (this may take a while) ... >>>>>>> Upgrade Step: import_distributions (this may take a while) ... >>>>>>> Upgrade Step: import_puppet_modules (this may take a while) ... >>>>>>> Upgrade Step: import_subscriptions (this may take a while) ... >>>>>>> Upgrade Step: elasticsearch_message... >>>>>>> Elasticsearch has been removed as a dependency. The database files >>>>>>> can be removed manually with #rm -rf /var/lib/elasticsearch. Some >>>>>>> packages >>>>>>> are no longer needed and can be removed: #rpm -e ruby193-rubygem-tire >>>>>>> tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java >>>>>>> lucene4-contrib >>>>>>> lucene4 >>>>>>> Upgrade Step: add_export_distributor (this may take a while) ... >>>>>>> Upgrade Step: remove_docker_v1_content (this may take a while) ... >>>>>>> Upgrade Step: update_puppet_repository_distributors (this may take a >>>>>>> while) ... >>>>>>> Upgrade Step: update_subscription_facet_backend_data (this may take >>>>>>> a while) ... >>>>>>> Upgrade step update_subscription_facet_backend_data failed. Check >>>>>>> logs for more information. >>>>>>> [root@wellkatello ~]# >>>>>>> >>>>>>> >>>>>>> I've created a ticket for it... >>>>>>> http://projects.theforeman.org/issues/15558 >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Foreman users" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to [email protected]. >>>>>>> To post to this group, send email to [email protected]. >>>>>>> Visit this group at https://groups.google.com/group/foreman-users. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to a topic in >>>>>> the Google Groups "Foreman users" group. >>>>>> To unsubscribe from this topic, visit >>>>>> https://groups.google.com/d/topic/foreman-users/86Pt-1v0L1s/unsubscribe >>>>>> . >>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>> [email protected]. >>>>>> To post to this group, send email to [email protected]. >>>>>> Visit this group at https://groups.google.com/group/foreman-users. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Foreman users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at https://groups.google.com/group/foreman-users. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Foreman users" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/foreman-users/86Pt-1v0L1s/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at https://groups.google.com/group/foreman-users. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Foreman users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://groups.google.com/group/foreman-users. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Eric D. Helms >> Red Hat Engineering >> Ph.D. Student - North Carolina State University >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Foreman users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/foreman-users/86Pt-1v0L1s/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > -- Eric D. Helms Red Hat Engineering Ph.D. Student - North Carolina State University -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
