Katello 3.0RC 2 strangeness

I have a fresh install of Katello 3.0 RC2 and I have noticed a couple
strange behaviors. I have 3 custom products. Centos 7.2 ( with epel,
updates, os repos ), a mesos product, and a Katello product. I have
created a content view for each product and brought them together into a
composite view.

  1. When creating an activation key for some reason the mesos product would
    not show up as a subscription to be added to the key

  2. When auto attach was set on the activation key and a machine
    subscribed. None of the subscriptions were added to the machine

  3. When created the centos 7.2 product it automatically created the 7.2
    Operating System. I setup a host using the 7.2 OS and after the machine
    was built something switched the Host definition back to the 7.0 Operating
    System causing certain issues since some of the templates were not
    associated with that OS. I am not sure why the Host OS would get changed.

It does not show up on the subscription page either.

I will create a bug for the OS issue

··· On Tuesday, April 19, 2016 at 9:25:10 AM UTC-4, Travis Camechis wrote: > > I have a fresh install of Katello 3.0 RC2 and I have noticed a couple > strange behaviors. I have 3 custom products. Centos 7.2 ( with epel, > updates, os repos ), a mesos product, and a Katello product. I have > created a content view for each product and brought them together into a > composite view. > > 1. When creating an activation key for some reason the mesos product > would not show up as a subscription to be added to the key > > 2. When auto attach was set on the activation key and a machine > subscribed. None of the subscriptions were added to the machine > > 3. When created the centos 7.2 product it automatically created the 7.2 > Operating System. I setup a host using the 7.2 OS and after the machine > was built something switched the Host definition back to the 7.0 Operating > System causing certain issues since some of the templates were not > associated with that OS. I am not sure why the Host OS would get changed. >

bug #14718

··· On Tuesday, April 19, 2016 at 9:25:10 AM UTC-4, Travis Camechis wrote: > > I have a fresh install of Katello 3.0 RC2 and I have noticed a couple > strange behaviors. I have 3 custom products. Centos 7.2 ( with epel, > updates, os repos ), a mesos product, and a Katello product. I have > created a content view for each product and brought them together into a > composite view. > > 1. When creating an activation key for some reason the mesos product > would not show up as a subscription to be added to the key > > 2. When auto attach was set on the activation key and a machine > subscribed. None of the subscriptions were added to the machine > > 3. When created the centos 7.2 product it automatically created the 7.2 > Operating System. I setup a host using the 7.2 OS and after the machine > was built something switched the Host definition back to the 7.0 Operating > System causing certain issues since some of the templates were not > associated with that OS. I am not sure why the Host OS would get changed. >

> I have a fresh install of Katello 3.0 RC2 and I have noticed a couple
> strange behaviors. I have 3 custom products. Centos 7.2 ( with epel,
> updates, os repos ), a mesos product, and a Katello product. I have
> created a content view for each product and brought them together into a
> composite view.
>
> 1. When creating an activation key for some reason the mesos product
> would not show up as a subscription to be added to the key

Does it show up on the 'subscriptions' page?

>
> 2. When auto attach was set on the activation key and a machine
> subscribed. None of the subscriptions were added to the machine
>

http://projects.theforeman.org/issues/14697

Should be fixed in the next RC

> 3. When created the centos 7.2 product it automatically created the 7.2
> Operating System. I setup a host using the 7.2 OS and after the machine
> was built something switched the Host definition back to the 7.0
> Operating System causing certain issues since some of the templates were
> not associated with that OS. I am not sure why the Host OS would get
> changed.

This is likely due to the new reporting of the operating system by
subscription-manager. After looking at a centos machine it appears that
centos is reported as '7' instead of '7.2' by subscription manager and
thus gets associated with Centos 7.0. Sadly foreman currently doesn't
differentiate between Operating System for provisioning and Operating
System reported via facts.

I guess we'll need to turn that auto reporting off for Centos or some
other workaround, do you mind filing an issue?

Thanks!

-Justin

··· On 04/19/2016 09:25 AM, Travis Camechis wrote:


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

> It does not show up on the subscription page either.

I believe the subscription issue may be fixed by:
http://projects.theforeman.org/issues/14722

I've assigned it to 3.0.0.

In the meantime you can fix it by running 'foreman-rake katello:reindex'

>
> I will create a bug for the OS issue

Let me know the issue # when you file.

-Justin

··· On 04/19/2016 02:51 PM, Travis Camechis wrote:

On Tuesday, April 19, 2016 at 9:25:10 AM UTC-4, Travis Camechis wrote:

I have a fresh install of Katello 3.0 RC2 and I have noticed a
couple strange behaviors.   I have 3 custom products.  Centos 7.2 (
with epel, updates, os repos ),  a mesos product, and a Katello
product.  I have created a content view for each product and brought
them together into a composite view.

1.  When creating an activation key for some reason the mesos
product would not show up as a subscription to be added to the key

2.  When auto attach was set on the activation key and a machine
subscribed.  None of the subscriptions were added to the machine

3.  When created the centos 7.2 product it automatically created the
7.2 Operating System.  I setup a host using the 7.2 OS and after the
machine was built something switched the Host definition back to the
7.0 Operating System causing certain issues since some of the
templates were not associated with that OS.  I am not sure why the
Host OS would get changed.


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

I have installed Katello RC4 and it appears that the OS is still switching.
This causes us to have to fix the host between each rebuild.

··· On Tuesday, April 19, 2016 at 4:35:10 PM UTC-4, Travis Camechis wrote: > > bug #14718 > > On Tuesday, April 19, 2016 at 9:25:10 AM UTC-4, Travis Camechis wrote: >> >> I have a fresh install of Katello 3.0 RC2 and I have noticed a couple >> strange behaviors. I have 3 custom products. Centos 7.2 ( with epel, >> updates, os repos ), a mesos product, and a Katello product. I have >> created a content view for each product and brought them together into a >> composite view. >> >> 1. When creating an activation key for some reason the mesos product >> would not show up as a subscription to be added to the key >> >> 2. When auto attach was set on the activation key and a machine >> subscribed. None of the subscriptions were added to the machine >> >> 3. When created the centos 7.2 product it automatically created the 7.2 >> Operating System. I setup a host using the 7.2 OS and after the machine >> was built something switched the Host definition back to the 7.0 Operating >> System causing certain issues since some of the templates were not >> associated with that OS. I am not sure why the Host OS would get changed. >> >