Re: [Spacewalk-list] Errata severity issue - invalid value "Na"

2018-07-13 Thread Avi Miller
.com > On Behalf Of Avi Miller > Sent: Thursday, July 12, 2018 1:13 PM > To: spacewalk-list@redhat.com > Subject: Re: [Spacewalk-list] Errata severity issue - invalid value "Na" > > Hey Jeffery, > >> On 12 Jul 2018, at 7:20 am, Kalchik, Jeffery >> wr

Re: [Spacewalk-list] Errata severity issue - invalid value "Na"

2018-07-12 Thread Kalchik, Jeffery
--Original Message- From: spacewalk-list-boun...@redhat.com On Behalf Of Avi Miller Sent: Thursday, July 12, 2018 1:13 PM To: spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] Errata severity issue - invalid value "Na" Hey Jeffery, > On 12 Jul 2018, at 7:20 am,

Re: [Spacewalk-list] Errata severity issue - invalid value "Na"

2018-07-12 Thread Avi Miller
Hey Jeffery, > On 12 Jul 2018, at 7:20 am, Kalchik, Jeffery wrote: > > The Spacewalk API docs don’t list a valid severity value of “Na”. RedHat’s > errata severity page specifically lists only 4 values and “Na” isn’t one of > them. Can you please open an SR so the ULN team can fix the

Re: [Spacewalk-list] Errata severity issue - invalid value "Na"

2018-07-12 Thread Robert Paschedag
Am 12. Juli 2018 16:20:40 MESZ schrieb "Kalchik, Jeffery" : >Good morning, all (or good afternoon, good evening, etc.) > >I've just discovered a rather unfortunate behavior, and I'm not >entirely sure how I'm going to address it. I came to discover it when >implementing channel changes as a

Re: [Spacewalk-list] Errata severity issue - invalid value "Na"

2018-07-12 Thread Robert Paschedag
Am 12. Juli 2018 16:20:40 MESZ schrieb "Kalchik, Jeffery" : >Good morning, all (or good afternoon, good evening, etc.) > >I've just discovered a rather unfortunate behavior, and I'm not >entirely sure how I'm going to address it. I came to discover it when >implementing channel changes as a

[Spacewalk-list] Errata severity issue - invalid value "Na"

2018-07-12 Thread Kalchik, Jeffery
Good morning, all (or good afternoon, good evening, etc.) I've just discovered a rather unfortunate behavior, and I'm not entirely sure how I'm going to address it. I came to discover it when implementing channel changes as a result of Oracle changing it's backend channel architecture (that's