The install docs are still referencing 3.3 as the latest stable versions
and referring to 3.4 as 3.4-RC.
···
On Monday, 29 May 2017 05:32:56 UTC+1, Eric Helms wrote:
>
> All,
>
> We are happy to announce the GA of Katello 3.4. Highlights of the release:
>
> * Better file repository content management
> * Advanced repository syncing options for recovery and repair
> * UI overhaul
> * Content view force republishing
> * Candlepin 2.0 support
> * Pulp 2.12.2
>
> Release Notes:
> https://theforeman.org/plugins/katello/3.4/release_notes/release_notes.html
>
> Installation:
> https://theforeman.org/plugins/katello/3.4/installation/index.html
>
> Upgrade:
> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>
> See the changelog for detailed feature issues and bug fixes:
> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md
>
> Bug reporting
> =============
> If you come across a bug in your testing, please file it and note the
> version of Katello or Foreman that you're using in the report.
>
> http://projects.theforeman.org/projects/katello/issues/new
>
> --
> Eric D. Helms
> Red Hat Engineering
>
I'd like to ask a question about the upgrade instructions.
In step 3, what does the line
yum update -y foreman-release-scl
do?
The other two lines make sense. This one, I don't quite understand.
We host Katello on katello, so there is some jiggery-pokery with
moving products and content views around,
and deploying them.
Adding a new product (pulp-3.4, client-3.4, candlepin-3.4,
katello-3.4, plugins-1.15, foreman-1.15 etc) is easy
enough as a sub for the other two lines in that instruction.
I'm not 100% sure what the foreman-release-scl does? We are tracking
the various extra repos as necessary,
I presume they are kept up to date, since they aren't as explicitly
versioned. (rhsc, sig, passenger, puppet).
I usually just ignore this step, but that is bad practice - what does it do?
cheers
L.
···
------
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."
The foreman-release-scl ensures that the necessary SCL epositories are
setup and configured for a typical installation. If you are importing all
the necessary repositories into Katello and using that yourself then I
wouldn't worry about it.
Eric
···
On Mon, May 29, 2017 at 8:51 PM, Lachlan Musicman wrote:
Thanks for all the hard work.
I’d like to ask a question about the upgrade instructions.
In step 3, what does the line
yum update -y foreman-release-scl
do?
The other two lines make sense. This one, I don’t quite understand.
We host Katello on katello, so there is some jiggery-pokery with moving products and content views around,
and deploying them.
Adding a new product (pulp-3.4, client-3.4, candlepin-3.4, katello-3.4, plugins-1.15, foreman-1.15 etc) is easy
enough as a sub for the other two lines in that instruction.
I’m not 100% sure what the foreman-release-scl does? We are tracking the various extra repos as necessary,
I presume they are kept up to date, since they aren’t as explicitly versioned. (rhsc, sig, passenger, puppet).
I usually just ignore this step, but that is bad practice - what does it do?
cheers
L.
“Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams.”
add the various new products (pulp-3.4, katello-3.4, foreman-1.15 etc)
to the Katello Content View (with or without removing pulp-3.3,
katello-3.3, foreman-1.14) via (in UI) Yum Content, Repository Selection
publish a new version of the Katello CV
publish a new version of the Utility Server Composite Content View which
includes the newly published Katello CV
confirm they exist by going into Content Views -> Utility Server ->
Versions -> Utility Server 38.0 -> Yum Content - Versions -> Yum
repositories and confirm that the products are now in the new version
promote the relevant host to the new Utility Server CCV
yum clean all, all good
yum upgrade doesn't recognise new repos. If I look into
/etc/yum.repos.d/redhat.repo and the new products aren't listed in that
file.
In order to get it to work, traditionally I've then performed:
If I promote the server to a new version I'd expect the changes to be
reflected in the repos available?
Am I doing something wrong with regard to how I'm managing my CV/CCVs or
pushing changes out?
Cheers
L.
···
------
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."
The foreman-release-scl ensures that the necessary SCL epositories are
setup and configured for a typical installation. If you are importing all
the necessary repositories into Katello and using that yourself then I
wouldn’t worry about it.
Eric
On Mon, May 29, 2017 at 8:51 PM, Lachlan Musicman datakid@gmail.com > wrote:
Thanks for all the hard work.
I’d like to ask a question about the upgrade instructions.
In step 3, what does the line
yum update -y foreman-release-scl
do?
The other two lines make sense. This one, I don’t quite understand.
We host Katello on katello, so there is some jiggery-pokery with moving products and content views around,
and deploying them.
Adding a new product (pulp-3.4, client-3.4, candlepin-3.4, katello-3.4, plugins-1.15, foreman-1.15 etc) is easy
enough as a sub for the other two lines in that instruction.
I’m not 100% sure what the foreman-release-scl does? We are tracking the various extra repos as necessary,
I presume they are kept up to date, since they aren’t as explicitly versioned. (rhsc, sig, passenger, puppet).
I usually just ignore this step, but that is bad practice - what does it do?
cheers
L.
“Mission Statement: To provide hope and inspiration for collective
action, to build collective power, to achieve collective transformation,
rooted in grief and rage but pointed towards vision and dreams.”
They've changed now. Might I have been hitting a cache?
···
On Tuesday, 30 May 2017 13:30:53 UTC+1, Eric Helms wrote:
>
> Duncan,
>
> Can you point me to which website page/link you are meaning?
>
> On Tue, May 30, 2017 at 8:20 AM, Duncan Innes > wrote:
>
>> The install docs are still referencing 3.3 as the latest stable versions
>> and referring to 3.4 as 3.4-RC.
>>
>>
>> On Monday, 29 May 2017 05:32:56 UTC+1, Eric Helms wrote:
>>>
>>> All,
>>>
>>> We are happy to announce the GA of Katello 3.4. Highlights of the
>>> release:
>>>
>>> * Better file repository content management
>>> * Advanced repository syncing options for recovery and repair
>>> * UI overhaul
>>> * Content view force republishing
>>> * Candlepin 2.0 support
>>> * Pulp 2.12.2
>>>
>>> Release Notes:
>>>
>>> https://theforeman.org/plugins/katello/3.4/release_notes/release_notes.html
>>>
>>> Installation:
>>> https://theforeman.org/plugins/katello/3.4/installation/index.html
>>>
>>> Upgrade:
>>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>>>
>>> See the changelog for detailed feature issues and bug fixes:
>>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md
>>>
>>> Bug reporting
>>> =============
>>> If you come across a bug in your testing, please file it and note the
>>> version of Katello or Foreman that you're using in the report.
>>>
>>> http://projects.theforeman.org/projects/katello/issues/new
>>>
>>> --
>>> Eric D. Helms
>>> Red Hat Engineering
>>>
>> --
>> 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.
>>
>
>
>
> --
> Eric D. Helms
> Red Hat Engineering
>
I have discovered that my traditional method was finally deprecated and it
didn't work.
But I also found that the slightly easier work around works:
subscription-manager repos
For whatever reason, that refreshes the redhat.repo.
cheers
L.
···
On 30 May 2017 at 11:40, Lachlan Musicman wrote:
Great, thanks.
I am seeing another issue:
add the various new products (pulp-3.4, katello-3.4, foreman-1.15 etc)
to the Katello Content View (with or without removing pulp-3.3,
katello-3.3, foreman-1.14) via (in UI) Yum Content, Repository Selection
publish a new version of the Katello CV
publish a new version of the Utility Server Composite Content View
which includes the newly published Katello CV
confirm they exist by going into Content Views -> Utility Server ->
Versions -> Utility Server 38.0 -> Yum Content - Versions -> Yum
repositories and confirm that the products are now in the new version
promote the relevant host to the new Utility Server CCV
yum clean all, all good
yum upgrade doesn’t recognise new repos. If I look into
/etc/yum.repos.d/redhat.repo and the new products aren’t listed in that
file.
In order to get it to work, traditionally I’ve then performed:
“Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams.”
···
On Tue, May 30, 2017 at 08:30:49AM -0400, Eric D Helms wrote:
> Duncan,
>
> Can you point me to which website page/link you are meaning?
–
Beste Grüße/Kind regards,
Evgeni Golov
Software Engineer
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O’Neill, Eric Shander
add the various new products (pulp-3.4, katello-3.4, foreman-1.15 etc)
to the Katello Content View (with or without removing pulp-3.3,
katello-3.3, foreman-1.14) via (in UI) Yum Content, Repository Selection
publish a new version of the Katello CV
publish a new version of the Utility Server Composite Content View
which includes the newly published Katello CV
confirm they exist by going into Content Views -> Utility Server ->
Versions -> Utility Server 38.0 -> Yum Content - Versions -> Yum
repositories and confirm that the products are now in the new version
promote the relevant host to the new Utility Server CCV
yum clean all, all good
yum upgrade doesn’t recognise new repos. If I look into
/etc/yum.repos.d/redhat.repo and the new products aren’t listed in that
file.
In order to get it to work, traditionally I’ve then performed:
I have discovered that my traditional method was finally deprecated and it
didn’t work.
But I also found that the slightly easier work around works:
subscription-manager repos
For whatever reason, that refreshes the redhat.repo.
cheers
L.
“Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams.”
So would "subscription-manager refresh".
When you change repos, your subscription changes, but it is not pulled
in on every yum invocation.
You can set full_refresh_on_yum = 1 in rhsm.conf, but even then not
every aspect is properly updated [1].
Also, I would suggest against using sub-man unregister && sub-man
register as a cluebat workaround. The subscription certificate is also
used for katello-agent, and if you don't restart it after doing the
sub-man dance, you end up without the ability to apply errata via
katello-agent.
···
On Tue, May 30, 2017 at 11:50:40AM +1000, Lachlan Musicman wrote:
> On 30 May 2017 at 11:40, Lachlan Musicman wrote:
>
> > Great, thanks.
> >
> > I am seeing another issue:
> >
> > - yum clean all, all good
> > - yum upgrade doesn't recognise new repos. If I look into
> > /etc/yum.repos.d/redhat.repo and the new products aren't listed in that
> > file.
> >
> > In order to get it to work, traditionally I've then performed:
> >
> > subscription-manager identity
> > subscription-manager unsubscribe
> > subscription-manager register --org="ACMI" --activationkey="Utility
> > Server"
>
> I have discovered that my traditional method was finally deprecated and it
> didn't work.
>
> But I also found that the slightly easier work around works:
>
> subscription-manager repos
>
> For whatever reason, that refreshes the redhat.repo.
–
Beste Grüße/Kind regards,
Evgeni Golov
Software Engineer
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O’Neill, Eric Shander
I have discovered that my traditional method was finally deprecated and
it
didn’t work.
But I also found that the slightly easier work around works:
subscription-manager repos
For whatever reason, that refreshes the redhat.repo.
So would “subscription-manager refresh”.
When you change repos, your subscription changes, but it is not pulled
in on every yum invocation.
You can set full_refresh_on_yum = 1 in rhsm.conf, but even then not
every aspect is properly updated [1].
Also, I would suggest against using sub-man unregister && sub-man
register as a cluebat workaround. The subscription certificate is also
used for katello-agent, and if you don’t restart it after doing the
sub-man dance, you end up without the ability to apply errata via
katello-agent.
“Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams.”
Can I ask - since the unregister, reregister workaround is cluebat, what
are we to do when the subscription-manager refresh doesn't work as you
state it does?
We have systems - that I've just updated - but are not finding the new
redhat.repo or the updates therein.
Whereas the unregister, reregister workaround is shown to work,
consistently.
cheers
L.
···
On 30 May 2017 at 16:31, Evgeni Golov wrote:
On Tue, May 30, 2017 at 11:50:40AM +1000, Lachlan Musicman wrote:
I have discovered that my traditional method was finally deprecated and
it
didn’t work.
But I also found that the slightly easier work around works:
subscription-manager repos
For whatever reason, that refreshes the redhat.repo.
So would “subscription-manager refresh”.
When you change repos, your subscription changes, but it is not pulled
in on every yum invocation.
You can set full_refresh_on_yum = 1 in rhsm.conf, but even then not
every aspect is properly updated [1].
Also, I would suggest against using sub-man unregister && sub-man
register as a cluebat workaround. The subscription certificate is also
used for katello-agent, and if you don’t restart it after doing the
sub-man dance, you end up without the ability to apply errata via
katello-agent.
"The antidote to apocalypticism is apocalyptic civics. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "
