[Katello] Applicable vs Installable errata

Hi

I have question regarding Applicable and Installable errata on content
hosts. This is from documentation:

With regard to Content Hosts, Errata is divided into two distinct
> classifications depending on whether or not the Errata is present in the
> Content Host’s Lifecycle Environment and Content View:
>
> - Applicable: the errata applies to one or more Content Hosts
> - Installable: the errata applies to one or more Content Hosts and is
> present in the Content Host’s Lifecycle Environment and Content View
>
>
As far as I understand errata which is filtered out of Content View (not
present in CV) is not Installable errata, but is Applicable errata. Am I
right? But the thing is - when I go to Content Host -> Errata, where I can
see Installable errata I see all erratas including those I have filtered
out of CV. Is it a bug and GUI shows Applicable errata instead of
Installable? Or bug in documentation?

For example, I have filtered out all kernel packages from CV. So these
packages should be Applicable but not Installable, but here is what I see:

<https://lh3.googleusercontent.com/-IB4y-cgbTQo/V9a4ShuQ7JI/AAAAAAAAADM/43cr_J6ORWo6LjwIjyPLXgvgioY4Iey3QCLcB/s1600/errata.JPG>

I see all kernel packages as installable, although I have filtered them out
and when I do yum check-update they do not appear as available update.

Katello 3.1

Edgars

Hey Edgars,

The documentation is correct so if you are seeing non-installable errata show up on that page then it is a bug.

Out of curiosity, if you go to /api/v2/hosts/2/errata?errata_restrict_applicable=true do you see a list of errata without kernel updates?

I think I see what the bug is and am happy to file it unless you want to.

Thanks,
Walden

··· ----- Original Message ----- From: "Edgars M." To: "Foreman users" Sent: Monday, September 12, 2016 10:17:06 AM Subject: [foreman-users] [Katello] Applicable vs Installable errata

Hi

I have question regarding Applicable and Installable errata on content
hosts. This is from documentation:

With regard to Content Hosts, Errata is divided into two distinct

classifications depending on whether or not the Errata is present in the
Content Host’s Lifecycle Environment and Content View:

  • Applicable: the errata applies to one or more Content Hosts
  • Installable: the errata applies to one or more Content Hosts and is
    present in the Content Host’s Lifecycle Environment and Content View

As far as I understand errata which is filtered out of Content View (not
present in CV) is not Installable errata, but is Applicable errata. Am I
right? But the thing is - when I go to Content Host -> Errata, where I can
see Installable errata I see all erratas including those I have filtered
out of CV. Is it a bug and GUI shows Applicable errata instead of
Installable? Or bug in documentation?

For example, I have filtered out all kernel packages from CV. So these
packages should be Applicable but not Installable, but here is what I see:

https://lh3.googleusercontent.com/-IB4y-cgbTQo/V9a4ShuQ7JI/AAAAAAAAADM/43cr_J6ORWo6LjwIjyPLXgvgioY4Iey3QCLcB/s1600/errata.JPG

I see all kernel packages as installable, although I have filtered them out
and when I do yum check-update they do not appear as available update.

Katello 3.1

Edgars


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.
To post to this group, send email to 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.

Hi Walden

I took one content host and compared web gui and API results, here is what
I see:

WebGUI:

<https://lh3.googleusercontent.com/-PeF_S4vcO5M/V9epm1vXo3I/AAAAAAAAADc/INhpPG345xkJYTn2ge-Ek_KV-IqpvkxjACLcB/s1600/errata.installable.JPG>

And this is if I call API:

[em@katello.local ~]$ curl
https://katello.local/api/v2/hosts/291/errata?errata_restrict_applicable=true
-u em | python -m json.tool | grep errata_id
Enter host password for user 'em':
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 59357 0 59357 0 0 74973 0 --:–:-- --:–:-- --:–:--
74945
"errata_id": "RHSA-2016:1664",
"errata_id": "RHSA-2015:1623",
"errata_id": "RHBA-2015:1827",
"errata_id": "RHBA-2016:1185",
"errata_id": "RHBA-2015:1466",
"errata_id": "RHSA-2015:1272",
"errata_id": "RHSA-2016:1406",
"errata_id": "RHSA-2016:0855",
"errata_id": "RHSA-2015:2636",
"errata_id": "RHBA-2015:1992",
"errata_id": "RHSA-2016:0494",
"errata_id": "RHBA-2016:0150",
"errata_id": "RHSA-2016:0715",

[em@katello.local ~]$ curl
https://katello.local/api/v2/hosts/291/errata?errata_restrict_installable=true
-u em | python -m json.tool | grep errata_id
Enter host password for user 'em':
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 59357 0 59357 0 0 15410 0 --:–:-- 0:00:03 --:–:--
15409
"errata_id": "RHSA-2016:1664",
"errata_id": "RHSA-2015:1623",
"errata_id": "RHBA-2015:1827",
"errata_id": "RHBA-2016:1185",
"errata_id": "RHBA-2015:1466",
"errata_id": "RHSA-2015:1272",
"errata_id": "RHSA-2016:1406",
"errata_id": "RHSA-2016:0855",
"errata_id": "RHSA-2015:2636",
"errata_id": "RHBA-2015:1992",
"errata_id": "RHSA-2016:0494",
"errata_id": "RHBA-2016:0150",
"errata_id": "RHSA-2016:0715",

As you can see result is the same. Please file a bug if you know what is
wrong.

Edgars

pirmdiena, 2016. gada 12. septembris 17:15:14 UTC+2, Walden Raines rakstīja:

··· > > Hey Edgars, > > The documentation is correct so if you are seeing non-installable errata > show up on that page then it is a bug. > > Out of curiosity, if you go to > /api/v2/hosts/2/errata?errata_restrict_applicable=true do you see a list of > errata without kernel updates? > > I think I see what the bug is and am happy to file it unless you want to. > > Thanks, > Walden > > ----- Original Message ----- > From: "Edgars M." <edgars...@gmail.com > > To: "Foreman users" <forema...@googlegroups.com > > Sent: Monday, September 12, 2016 10:17:06 AM > Subject: [foreman-users] [Katello] Applicable vs Installable errata > > Hi > > I have question regarding Applicable and Installable errata on content > hosts. This is from documentation: > > With regard to Content Hosts, Errata is divided into two distinct > > classifications depending on whether or not the Errata is present in the > > Content Host’s Lifecycle Environment and Content View: > > > > - Applicable: the errata applies to one or more Content Hosts > > - Installable: the errata applies to one or more Content Hosts and is > > present in the Content Host’s Lifecycle Environment and Content View > > > > > As far as I understand errata which is filtered out of Content View (not > present in CV) is not Installable errata, but is Applicable errata. Am I > right? But the thing is - when I go to Content Host -> Errata, where I can > see Installable errata I see all erratas including those I have filtered > out of CV. Is it a bug and GUI shows Applicable errata instead of > Installable? Or bug in documentation? > > For example, I have filtered out all kernel packages from CV. So these > packages should be Applicable but not Installable, but here is what I see: > > < > https://lh3.googleusercontent.com/-IB4y-cgbTQo/V9a4ShuQ7JI/AAAAAAAAADM/43cr_J6ORWo6LjwIjyPLXgvgioY4Iey3QCLcB/s1600/errata.JPG> > > > > I see all kernel packages as installable, although I have filtered them > out > and when I do yum check-update they do not appear as available update. > > > Katello 3.1 > > > Edgars > > > -- > 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-user...@googlegroups.com . > To post to this group, send email to forema...@googlegroups.com > . > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. >

Hey Edgars,

Sorry for the delay in my response but I have two more questions.

  1. Does the kernel errata mentioned below show up as applicable or installable on the errata list page (/errata)?
  2. Just making sure everything is plugged in but you did publish a new version of the CV after creating the filter(s), correct?

Thanks,
Walden

··· ----- Original Message ----- From: "Edgars M." To: "Foreman users" Sent: Tuesday, September 13, 2016 3:31:23 AM Subject: Re: [foreman-users] [Katello] Applicable vs Installable errata

Hi Walden

I took one content host and compared web gui and API results, here is what
I see:

WebGUI:

https://lh3.googleusercontent.com/-PeF_S4vcO5M/V9epm1vXo3I/AAAAAAAAADc/INhpPG345xkJYTn2ge-Ek_KV-IqpvkxjACLcB/s1600/errata.installable.JPG

And this is if I call API:

[em@katello.local ~]$ curl
https://katello.local/api/v2/hosts/291/errata?errata_restrict_applicable=true
-u em | python -m json.tool | grep errata_id
Enter host password for user ‘em’:
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 59357 0 59357 0 0 74973 0 --:–:-- --:–:-- --:–:--
74945
"errata_id": “RHSA-2016:1664”,
“errata_id”: “RHSA-2015:1623”,
“errata_id”: “RHBA-2015:1827”,
“errata_id”: “RHBA-2016:1185”,
“errata_id”: “RHBA-2015:1466”,
“errata_id”: “RHSA-2015:1272”,
“errata_id”: “RHSA-2016:1406”,
“errata_id”: “RHSA-2016:0855”,
“errata_id”: “RHSA-2015:2636”,
“errata_id”: “RHBA-2015:1992”,
“errata_id”: “RHSA-2016:0494”,
“errata_id”: “RHBA-2016:0150”,
“errata_id”: “RHSA-2016:0715”,

[em@katello.local ~]$ curl
https://katello.local/api/v2/hosts/291/errata?errata_restrict_installable=true
-u em | python -m json.tool | grep errata_id
Enter host password for user ‘em’:
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 59357 0 59357 0 0 15410 0 --:–:-- 0:00:03 --:–:--
15409
"errata_id": “RHSA-2016:1664”,
“errata_id”: “RHSA-2015:1623”,
“errata_id”: “RHBA-2015:1827”,
“errata_id”: “RHBA-2016:1185”,
“errata_id”: “RHBA-2015:1466”,
“errata_id”: “RHSA-2015:1272”,
“errata_id”: “RHSA-2016:1406”,
“errata_id”: “RHSA-2016:0855”,
“errata_id”: “RHSA-2015:2636”,
“errata_id”: “RHBA-2015:1992”,
“errata_id”: “RHSA-2016:0494”,
“errata_id”: “RHBA-2016:0150”,
“errata_id”: “RHSA-2016:0715”,

As you can see result is the same. Please file a bug if you know what is
wrong.

Edgars

pirmdiena, 2016. gada 12. septembris 17:15:14 UTC+2, Walden Raines rakstīja:

Hey Edgars,

The documentation is correct so if you are seeing non-installable errata
show up on that page then it is a bug.

Out of curiosity, if you go to
/api/v2/hosts/2/errata?errata_restrict_applicable=true do you see a list of
errata without kernel updates?

I think I see what the bug is and am happy to file it unless you want to.

Thanks,
Walden

----- Original Message -----
From: “Edgars M.” <edgars...@gmail.com <javascript:>>
To: “Foreman users” <forema...@googlegroups.com <javascript:>>
Sent: Monday, September 12, 2016 10:17:06 AM
Subject: [foreman-users] [Katello] Applicable vs Installable errata

Hi

I have question regarding Applicable and Installable errata on content
hosts. This is from documentation:

With regard to Content Hosts, Errata is divided into two distinct

classifications depending on whether or not the Errata is present in the
Content Host’s Lifecycle Environment and Content View:

  • Applicable: the errata applies to one or more Content Hosts
  • Installable: the errata applies to one or more Content Hosts and is
    present in the Content Host’s Lifecycle Environment and Content View

As far as I understand errata which is filtered out of Content View (not
present in CV) is not Installable errata, but is Applicable errata. Am I
right? But the thing is - when I go to Content Host -> Errata, where I can
see Installable errata I see all erratas including those I have filtered
out of CV. Is it a bug and GUI shows Applicable errata instead of
Installable? Or bug in documentation?

For example, I have filtered out all kernel packages from CV. So these
packages should be Applicable but not Installable, but here is what I see:

<
https://lh3.googleusercontent.com/-IB4y-cgbTQo/V9a4ShuQ7JI/AAAAAAAAADM/43cr_J6ORWo6LjwIjyPLXgvgioY4Iey3QCLcB/s1600/errata.JPG>

I see all kernel packages as installable, although I have filtered them
out
and when I do yum check-update they do not appear as available update.

Katello 3.1

Edgars


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-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


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.
To post to this group, send email to 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.

Hi

  1. It shows as installable
  2. Yes, published and promoted

I filed a bug Bug #16544: Katello 3.x does not show Installable errata, only applicable - Katello - Foreman

Edgars

ceturtdiena, 2016. gada 15. septembris 15:30:39 UTC+2, Walden Raines
rakstīja:

··· > > Hey Edgars, > > Sorry for the delay in my response but I have two more questions. > > 1. Does the kernel errata mentioned below show up as applicable or > installable on the errata list page (/errata)? > 2. Just making sure everything is plugged in but you did publish a new > version of the CV after creating the filter(s), correct? > > Thanks, > Walden > > > ----- Original Message ----- > From: "Edgars M." <edgars...@gmail.com > > To: "Foreman users" <forema...@googlegroups.com > > Sent: Tuesday, September 13, 2016 3:31:23 AM > Subject: Re: [foreman-users] [Katello] Applicable vs Installable errata > > Hi Walden > > I took one content host and compared web gui and API results, here is what > I see: > > WebGUI: > > < > https://lh3.googleusercontent.com/-PeF_S4vcO5M/V9epm1vXo3I/AAAAAAAAADc/INhpPG345xkJYTn2ge-Ek_KV-IqpvkxjACLcB/s1600/errata.installable.JPG> > > > > And this is if I call API: > > > [em@katello.local ~]$ curl > > https://katello.local/api/v2/hosts/291/errata?errata_restrict_applicable=true > -u em | python -m json.tool | grep errata_id > Enter host password for user 'em': > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 59357 0 59357 0 0 74973 0 --:--:-- --:--:-- --:--:-- > 74945 > "errata_id": "RHSA-2016:1664", > "errata_id": "RHSA-2015:1623", > "errata_id": "RHBA-2015:1827", > "errata_id": "RHBA-2016:1185", > "errata_id": "RHBA-2015:1466", > "errata_id": "RHSA-2015:1272", > "errata_id": "RHSA-2016:1406", > "errata_id": "RHSA-2016:0855", > "errata_id": "RHSA-2015:2636", > "errata_id": "RHBA-2015:1992", > "errata_id": "RHSA-2016:0494", > "errata_id": "RHBA-2016:0150", > "errata_id": "RHSA-2016:0715", > > > [em@katello.local ~]$ curl > > https://katello.local/api/v2/hosts/291/errata?errata_restrict_installable=true > -u em | python -m json.tool | grep errata_id > Enter host password for user 'em': > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 59357 0 59357 0 0 15410 0 --:--:-- 0:00:03 --:--:-- > 15409 > "errata_id": "RHSA-2016:1664", > "errata_id": "RHSA-2015:1623", > "errata_id": "RHBA-2015:1827", > "errata_id": "RHBA-2016:1185", > "errata_id": "RHBA-2015:1466", > "errata_id": "RHSA-2015:1272", > "errata_id": "RHSA-2016:1406", > "errata_id": "RHSA-2016:0855", > "errata_id": "RHSA-2015:2636", > "errata_id": "RHBA-2015:1992", > "errata_id": "RHSA-2016:0494", > "errata_id": "RHBA-2016:0150", > "errata_id": "RHSA-2016:0715", > > > > As you can see result is the same. Please file a bug if you know what is > wrong. > > > Edgars > > > > pirmdiena, 2016. gada 12. septembris 17:15:14 UTC+2, Walden Raines > rakstīja: > > > > Hey Edgars, > > > > The documentation is correct so if you are seeing non-installable errata > > show up on that page then it is a bug. > > > > Out of curiosity, if you go to > > /api/v2/hosts/2/errata?errata_restrict_applicable=true do you see a list > of > > errata without kernel updates? > > > > I think I see what the bug is and am happy to file it unless you want > to. > > > > Thanks, > > Walden > > > > ----- Original Message ----- > > From: "Edgars M." <edgars...@gmail.com > > > To: "Foreman users" <forema...@googlegroups.com > > > Sent: Monday, September 12, 2016 10:17:06 AM > > Subject: [foreman-users] [Katello] Applicable vs Installable errata > > > > Hi > > > > I have question regarding Applicable and Installable errata on content > > hosts. This is from documentation: > > > > With regard to Content Hosts, Errata is divided into two distinct > > > classifications depending on whether or not the Errata is present in > the > > > Content Host’s Lifecycle Environment and Content View: > > > > > > - Applicable: the errata applies to one or more Content Hosts > > > - Installable: the errata applies to one or more Content Hosts and > is > > > present in the Content Host’s Lifecycle Environment and Content > View > > > > > > > > As far as I understand errata which is filtered out of Content View (not > > present in CV) is not Installable errata, but is Applicable errata. Am I > > right? But the thing is - when I go to Content Host -> Errata, where I > can > > see Installable errata I see all erratas including those I have filtered > > out of CV. Is it a bug and GUI shows Applicable errata instead of > > Installable? Or bug in documentation? > > > > For example, I have filtered out all kernel packages from CV. So these > > packages should be Applicable but not Installable, but here is what I > see: > > > > < > > > https://lh3.googleusercontent.com/-IB4y-cgbTQo/V9a4ShuQ7JI/AAAAAAAAADM/43cr_J6ORWo6LjwIjyPLXgvgioY4Iey3QCLcB/s1600/errata.JPG> > > > > > > > > > I see all kernel packages as installable, although I have filtered them > > out > > and when I do yum check-update they do not appear as available update. > > > > > > Katello 3.1 > > > > > > Edgars > > > > > > -- > > 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-user...@googlegroups.com . > > To post to this group, send email to forema...@googlegroups.com > > . > > Visit this group at https://groups.google.com/group/foreman-users. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > 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-user...@googlegroups.com . > To post to this group, send email to forema...@googlegroups.com > . > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. >