The new CP version is SAM 1.2 should help this.

The new candlepi,, 07.17.1, is in the current pudddle.

I verified this yesterday.

This (long) update is a bit of an FYI (and warning) about applying the hotfix packages ...

Just letting you know that while attempting to resolve BZ887124, we had the customer use the hotfix packages mentioned in comment #2.  They didn't fix the issue, but we eventually got it fixed (see the other BZ).  But anyway, with the hotfix packages the customer reported the following problem:

<customer>
After clicking System->Systename I get following error.

Candlepin::CandlepinResource: 500 Internal Server Error {"displayMessage":"Runtime Error TypeError: Cannot find function getHostConsumer in object org.candlepin.policy.js.entitlement.PreEntHelper@6a8cd8f0. (rules#409) at org.mozilla.javascript.ScriptRuntime.constructError:3,654"} (GET /candlepin/pools/?consumer=b37050ac-5069-4bcc-b1d1-fec1c2e95a3a&listall=false)

This happens when cklicking any system.
</customer>

-------------------------------------------------------------------------------------------------------

It seems in the hotfix packages the PreEntHelper class is missing the getHostConsumer method.

Looking at the original candlepin packages on SAM1.1 I can see that method:
<original_packages>
[root@sam entitlement]# rpm -qa | grep candlepin
candlepin-0.6.5-1.el6_2.noarch
candlepin-tomcat6-0.6.5-1.el6_2.noarch

[root@sam ~]# locate PreEntHelper.class
/var/lib/tomcat6/webapps/candlepin/WEB-INF/classes/org/candlepin/policy/js/entitlement/PreEntHelper.class

[root@sam ~]# locate PreEntHelper.class | xargs rpm -qf
candlepin-tomcat6-0.6.5-1.el6_2.noarch

[root@sam ~]# locate PreEntHelper.class | xargs grep -a getHostConsumer
addWarning	getResult)()Lorg/candlepin/policy/ValidationResult;
StackMapTablegetHostConsumer
(Ljava/lang/String;)Lorg/candlepin/model/Consumer;guestId/ReadOnlyPool;

... and the getHostConsumer method is there
</original_packages>


But looking at the hotfix packages I can see that it is missing:

<hotfix_packages>
[root@vm89 ~]# rpm -qa | grep candlepin
candlepin-0.6.7.1-1.el6_2.noarch
candlepin-tomcat6-0.6.7.1-1.el6_2.noarch

[root@vm89 ~]# locate PreEntHelper.class
/var/lib/tomcat6/webapps/candlepin/WEB-INF/classes/org/candlepin/policy/js/entitlement/PreEntHelper.class
[root@vm89 ~]# locate PreEntHelper.class | xargs rpm -qf
candlepin-tomcat6-0.6.7.1-1.el6_2.noarch
[root@vm89 ~]# locate PreEntHelper.class | xargs grep -a getHostConsumer
[root@vm89 ~]# 

... getHostConsumer method is missing.
</hotfix_packages>

-------------------------------------------------------------------------------------------------------

So I tried adding the method back into the hotfix packages:

<attempt_to_add_missing_method>
Ok, I was able to get a copy of the hotfix source package here:
https://brewweb.devel.redhat.com/buildinfo?buildID=225464

# rpm -ivh candlepin-0.6.7.1-1.el6_2.src.rpm
...
/root/rpmbuild/SOURCES/candlepin-0.6.7.1/src/main/java/org/candlepin/policy/js/entitlement/PreEntHelper.java

However, its not as easy as just adding the missing getHostConsumer method to the PreEntHelper.java file.

    public Consumer getHostConsumer(String guestId) {
        return consumerCurator.getHost(guestId);
    }

[root@vm89 entitlement]# javac -extdirs /var/lib/tomcat6/webapps/candlepin/WEB-INF/lib/ -classpath /var/lib/tomcat6/webapps/candlepin/WEB-INF/classes PreEntHelper.java
PreEntHelper.java:105: cannot find symbol
symbol  : variable consumerCurator
location: class org.candlepin.policy.js.entitlement.PreEntHelper
        return consumerCurator.getHost(guestId);
               ^
1 error

The way the PreEntHelper class is constructed is different between the SAM 1.1 release containing candlepin-tomcat6-0.6.5-1.el6_2.noarch and the candlepin-tomcat6-0.6.7.1-1.el6_2.noarch in the hotfix package.  The hotfix release no longer has reference to Consumers and ConsumerCurators.
</attempt_to_add_missing_method>

-------------------------------------------------------------------------------------------------------

So I had to give up trying to re-add the method and just get the customer to revert back to the original candlepin packages on SAM1.1:

# yum downgrade candlepin candlepin-selinux candlepin-tomcat6
... which installs the original versions

Currently waiting for the customers feedback that this works.  I was a little concerned about what change this introduced: /usr/share/candlepin/cpdb --update in comment #2, but it seems that it only added indexes to the foreign keys, so I'm assuming it will be ok to just downgrade the packages and the earlier version of candlepin won't have any problems in interacting with the DB, even though the DB was updated.

-- Mark

Mark this is definitely a separate issue and could be filed as such, but I believe I can provide a workaround. 

We can see this breaking in commit: 85703e05c8fa4ae6cb5d949f5caafcbf2953fce0 which was done in the hotfix branch between 0.6.6 and 0.6.7. The java to javascript API changed in that something was removed, but the customer's deployment likely already has a newer rules file in their database from a manifest import.

I believe you can safely workaround by having customer delete whatever is in the cp_rules table in the candlepin postgresql database. This would force the server to use the rules file included in the RPM. I don't know the credentials in a SAM deployment to hit the Candlepin database but once in, it should just be a simple "delete from cp_rules;" After this they should be able to use the new hotfix package.

Thanks for the update Devan.  I have passed this information onto the customer and am waiting on their feedback.  I'm not sure if they have already downgraded the candlepin packages or if they will try the SQL.  Will let you know.

BTW I have filed another BZ for this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=917947

Thanks,
Mark

Hi Devan,

The customer has confirmed that running "delete from cp_rules;" fixed the problem for them.  They didn't need to downgrade the hotfix packages back to the GA packages.

Thanks for the help,
Mark

Closing out verified bugs from 1.2. Somehow the errata tool missed them.

Closing out verified bugs from 1.2. Somehow the errata tool missed them.