Description of problem: I did an upgrade from sat6.1.9 -> sat6.2 GA snap15.1. I defined a rule before upgrade and associated "Default Org" and Default Loc". Later, once upgrade was completed successfully when I checked the created rule before upgrade, I don't find it under Default Org. Org/location auto got disassociated. Version-Release number of selected component (if applicable): upgrade from sat6.1.9 -> sat6.2 GA snap15.1. How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: org/location association with discovery rule should remain there Additional info:
Created attachment 1166331 [details] foreman-debug
Lukas, can you take a quick look at this bug?
Sachin, are you using administrator account when encountering the missing taxonomy? We added new permissions, check discovery rules permissions for the user in order to have full access there. We also now enforce discovery rule to match hostgroup taxonomy, is hostgroup also associated to the org/loc? If not, rule can't be added to the taxonomy. What was the foreman_discovery RPM version before and after upgrade please? I can't find it in the logs.
Yes. I created a discovery rule with admin account on sat6.1.9. "Default_Organization" and "Default_Location" were associated before upgrade and hostgroup was associated too with discovery rule. Please see the attached screenshot where hostgroup is associated with rule but no org/location after upgrade I'll share the discovery rpm version
Created attachment 1167258 [details] hostgroup associated with discovery rule but no org/location after upgrade
I am not sure I understand, Any context gives you all org/loc, can you attach screenshot of the detail (edit) page of the rule (its taxonomy)?
I just installed sat619 and realized that in sat619, we don't have tabs to select org and locations while creating the discovery rule. However in 6.2, I do see separate tabs for organization and location selection. So in this case, I'm assuming all defined rules with 6.1.9 (when no org/loc was selected explicitly) automatically be disassociated after upgrade with 6.2. Looks like its more a documentation issue.
Created attachment 1167387 [details] in 6.1.9, no separte tabs under discovery rule to select org/location
I'm closing this bz as behaviour is expected. But I'll ask documentation team to add a note in upgrade docs. Note: After 6.2 upgrade, users needs to explicitly associate selected org/location with discovery rules.
Looks like a good upgrading instruction, thanks.