Created attachment 1027149 [details] after upgrade webUI shows two default orgs Description of problem: After upgrade, webUI shows two default orgs - Default Organization - Default_Organization Version-Release number of selected component (if applicable): upgrade[sat6.0.8 --> sat6.1 GA snap4], How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: UI shows two default org Expected results: I think 'Default Organization' is default org in sat6.1 so this should be visible in UI and without any association loss with 'Default_Organization'. It means all entities associated to Default_Organization should be associated to 'Default Organization' after upgrade. Additional info:
I don't think you should get two organizations. Users coming from 6.0 will have "Default_Organization" only, "Default Organzation" without the underscore will only be 6.1 and later new installs. I'll try tomorrow to see what happens. Did you happen to wipe out the answer file somehow?
After upgrade every time I see two orgs 1. Default_Organozation ( default org in sat6.0, before upgrade) 2. Default Organization ( default org in sat6.1, after upgrade) I didn't wipe out the answer file manually. I'll double check again. Thanks
Created redmine issue http://projects.theforeman.org/issues/10695 from this bug
Another update.. Today I tried upgrade [sat6.0.8 -> sat6.1 snap7] on rhel66. On rhel66, I can see only one org i.e. 'Default_organization' after upgrade. And on rhel71, I can see two Default orgs after upgrade as mentioned in comment3. What is expected here ?
Yeah, On IRC, dev(Stephen) confirmed that user should see the 6.0 org after upgrade i.e. Default_Organization.
Moving to POST since upstream bug http://projects.theforeman.org/issues/10695 has been closed ------------- Anonymous Applied in changeset commit:026fa1d903ee04589ad5dd3272142293a7b45c8c.
Verified with sat6.1 GA snap8. Upgrade was successful on sat6 and I can see only one org after upgrade on rhel71 platform. Thank you for the fix. -- [root@sat6-rhel71-custom-certs ownca]# katello-installer --upgrade --certs-server-cert ./sat6-rhel71-custom-certs.usersys.redhat.com/sat6-rhel71-custom-certs.usersys.redhat.com.crt --certs-server-cert-req ./sat6-rhel71-custom-certs.usersys.redhat.com/sat6-rhel71-custom-certs.usersys.redhat.com.crt.req --certs-server-key ./sat6-rhel71-custom-certs.usersys.redhat.com/sat6-rhel71-custom-certs.usersys.redhat.com.key --certs-server-ca-cert ./cacert.crt Upgrading... Upgrade Step: stop_services... Upgrade Step: start_mongo... Upgrade Step: migrate_pulp... Upgrade Step: migrate_candlepin... Upgrade Step: migrate_foreman... Upgrade Step: Running installer... Installing Done [100%] [..................................................................] The full log is at /var/log/katello-installer/katello-installer.log Upgrade Step: Restarting services... Upgrade Step: db:seed... Upgrade Step: Running errata import task (this may take a while)... Upgrade Step: Update gpg key urls to support capsule isolation (this may take a while)... Upgrade Step: Update repositories to specify metadata_expire (this may take a while)... Katello upgrade completed!
This bug is slated to be released with Satellite 6.1.
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.