Bug 1222896 - After upgrade[sat6.0.8 --> sat6.1 GA snap4], webUI shows two default orgs
Summary: After upgrade[sat6.0.8 --> sat6.1 GA snap4], webUI shows two default orgs
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: Stephen Benjamin
QA Contact: Sachin Ghai
URL: http://projects.theforeman.org/issues...
Depends On:
Blocks: Red Hat1195450
TreeView+ depends on / blocked
Reported: 2015-05-19 12:08 UTC by Sachin Ghai
Modified: 2017-02-23 20:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-08-12 13:58:15 UTC
Target Upstream Version:

Attachments (Terms of Use)
after upgrade webUI shows two default orgs (128.78 KB, image/png)
2015-05-19 12:08 UTC, Sachin Ghai
no flags Details

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 10695 0 None None None 2016-04-22 14:58:49 UTC

Description Sachin Ghai 2015-05-19 12:08:40 UTC
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:

Steps to Reproduce:

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:

Comment 2 Stephen Benjamin 2015-06-02 21:46:42 UTC
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?

Comment 3 Sachin Ghai 2015-06-03 05:44:24 UTC
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

Comment 4 Stephen Benjamin 2015-06-03 17:55:29 UTC
Created redmine issue http://projects.theforeman.org/issues/10695 from this bug

Comment 5 Sachin Ghai 2015-06-04 11:18:50 UTC
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 ?

Comment 6 Sachin Ghai 2015-06-04 13:48:12 UTC
Yeah, On IRC, dev(Stephen) confirmed that user should see the 6.0 org after upgrade i.e. Default_Organization.

Comment 7 Bryan Kearney 2015-06-05 18:05:52 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/10695 has been closed
Applied in changeset commit:026fa1d903ee04589ad5dd3272142293a7b45c8c.

Comment 10 Sachin Ghai 2015-06-11 13:46:59 UTC
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 
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!

Comment 11 Bryan Kearney 2015-08-11 13:32:45 UTC
This bug is slated to be released with Satellite 6.1.

Comment 12 Bryan Kearney 2015-08-12 13:58:15 UTC
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.

Note You need to log in before you can comment on or make changes to this bug.