#13128 - content host update no longer accepts facts and service_level

Recently (past week?) I am unable to update content host facts or service_level via API. Does this sound familiar to anyone?

··· --

@thomasmckay

>
> Recently (past week?) I am unable to update content host facts or
> service_level via API. Does this sound familiar to anyone?
>
> do you happen to get an error? are you sure those attributes are allowed
via attr_accessible?

··· On Tue, Jan 12, 2016 at 1:51 PM, Tom McKay wrote:

@thomasmckay


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

I'm mostly hoping a katello dev sees this and recalls the change. These attributes were, before host unification and scoped search, coming directly from candlepin.

··· ----- Original Message ----- > On Tue, Jan 12, 2016 at 1:51 PM, Tom McKay wrote: > > > > > Recently (past week?) I am unable to update content host facts or > > service_level via API. Does this sound familiar to anyone? > > > > do you happen to get an error? are you sure those attributes are allowed > via attr_accessible? >

Nevermind. I think master/develop are in too much churn to expect things to work. :slight_smile:

This issue was due to SETTINGS[:katello][:use_cp] being nil which is a result, I believe, of the work trying to resolve assets.

··· ----- Original Message ----- > > > ----- Original Message ----- > > On Tue, Jan 12, 2016 at 1:51 PM, Tom McKay wrote: > > > > > > > > Recently (past week?) I am unable to update content host facts or > > > service_level via API. Does this sound familiar to anyone? > > > > > > do you happen to get an error? are you sure those attributes are allowed > > via attr_accessible? > > > > > I'm mostly hoping a katello dev sees this and recalls the change. These > attributes were, before host unification and scoped search, coming directly > from candlepin. > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. >

That value was nil due to asset churn. Most recent updates to my PR should
fix that.

··· On Jan 12, 2016 7:15 AM, "Tom McKay" wrote:

----- Original Message -----

----- Original Message -----

On Tue, Jan 12, 2016 at 1:51 PM, Tom McKay thomasmckay@redhat.com > wrote:

Recently (past week?) I am unable to update content host facts or
service_level via API. Does this sound familiar to anyone?

do you happen to get an error? are you sure those attributes are
allowed

via attr_accessible?

I’m mostly hoping a katello dev sees this and recalls the change. These
attributes were, before host unification and scoped search, coming
directly
from candlepin.


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Nevermind. I think master/develop are in too much churn to expect things
to work. :slight_smile:

This issue was due to SETTINGS[:katello][:use_cp] being nil which is a
result, I believe, of the work trying to resolve assets.


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.