There have been comments and release notes around EL6 support but I wanted
to take the time to make sure users see the information and are aware of
the deprecations.
As of Foreman 1.13, EL6 was officially dropped as a supported operating
system. An official repository of EL6 builds exists for 1.13 extending the
life of Foreman on EL6 for that release and that release alone.
The Katello 3.2 release is the last release stream that will have support
for EL6. For Katello 3.3 and beyond, only EL7 releases will be made
available. We will be working on a strategy to help users migrate their EL6
installations to EL7 and please reach out to us if you have questions
regrading this.
Further, we recommend ALL new installs of 1.13 or 3.2 be done on an EL7 box.
To reiterate, Foreman 1.14 and Katello 3.2 will NOT be provided on EL6. The
1.13 and 3.2 streams will continue to receive updates per our normal
support policy.
>
> We will be working on a strategy to help users migrate their EL6
> installations to EL7 and please reach out to us if you have questions
> regrading this.
>
I have an existing EL6 installation that I wish ti migrate to EL7, is there
some documentation that I can look at work someone specifically I should
talk to in order to get an idea on what this process is.
Thank You
Michael
···
On Thursday, December 1, 2016 at 7:31:49 AM UTC-8, Eric Helms wrote:
>
> All,
>
> There have been comments and release notes around EL6 support but I wanted
> to take the time to make sure users see the information and are aware of
> the deprecations.
>
> As of Foreman 1.13, EL6 was officially dropped as a supported operating
> system. An official repository of EL6 builds exists for 1.13 extending the
> life of Foreman on EL6 for that release and that release alone.
>
> The Katello 3.2 release is the last release stream that will have support
> for EL6. For Katello 3.3 and beyond, only EL7 releases will be made
> available. We will be working on a strategy to help users migrate their EL6
> installations to EL7 and please reach out to us if you have questions
> regrading this.
>
> Further, we recommend ALL new installs of 1.13 or 3.2 be done on an EL7
> box.
>
> To reiterate, Foreman 1.14 and Katello 3.2 will NOT be provided on EL6.
> The 1.13 and 3.2 streams will continue to receive updates per our normal
> support policy.
>
> --
> Eric D. Helms
> Red Hat Engineering
>
>
There is a tool that got built for the Satellite product for doing this
sort of migration that uses upstream bits so in theory it should work [1].
I'm CC'ing John who developed it to give some more insight.
···
On Tue, Jun 13, 2017 at 6:47 PM, Michael Bassler wrote:
We will be working on a strategy to help users migrate their EL6
installations to EL7 and please reach out to us if you have questions
regrading this.
I have an existing EL6 installation that I wish ti migrate to EL7, is
there some documentation that I can look at work someone specifically I
should talk to in order to get an idea on what this process is.
Thank You
Michael
On Thursday, December 1, 2016 at 7:31:49 AM UTC-8, Eric Helms wrote:
All,
There have been comments and release notes around EL6 support but I
wanted to take the time to make sure users see the information and are
aware of the deprecations.
As of Foreman 1.13, EL6 was officially dropped as a supported operating
system. An official repository of EL6 builds exists for 1.13 extending the
life of Foreman on EL6 for that release and that release alone.
The Katello 3.2 release is the last release stream that will have support
for EL6. For Katello 3.3 and beyond, only EL7 releases will be made
available. We will be working on a strategy to help users migrate their EL6
installations to EL7 and please reach out to us if you have questions
regrading this.
Further, we recommend ALL new installs of 1.13 or 3.2 be done on an EL7
box.
To reiterate, Foreman 1.14 and Katello 3.2 will NOT be provided on EL6.
The 1.13 and 3.2 streams will continue to receive updates per our normal
support policy.
Unfortunately, the RHEL 6 > 7 part of the clone tool is not upstream, as it
was developed retroactively (after upstream was changed to RHEL 7 only),
but there is talk of adding this upstream. Here are the parts that we found
when restoring a RHEL6 backup on RHEL 7.
We had to restore .dump files from an online backup
Let us know how it goes or if you have any questions, I'm also cc'ing
Suresh who did work on this feature, he may be able to go over anything I
missed.
-John
John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch
···
On Wed, Jun 14, 2017 at 8:32 AM, Eric D Helms wrote:
Hi Michael,
There is a tool that got built for the Satellite product for doing this
sort of migration that uses upstream bits so in theory it should work [1].
I’m CC’ing John who developed it to give some more insight.
We will be working on a strategy to help users migrate their EL6
installations to EL7 and please reach out to us if you have questions
regrading this.
I have an existing EL6 installation that I wish ti migrate to EL7, is
there some documentation that I can look at work someone specifically I
should talk to in order to get an idea on what this process is.
Thank You
Michael
On Thursday, December 1, 2016 at 7:31:49 AM UTC-8, Eric Helms wrote:
All,
There have been comments and release notes around EL6 support but I
wanted to take the time to make sure users see the information and are
aware of the deprecations.
As of Foreman 1.13, EL6 was officially dropped as a supported operating
system. An official repository of EL6 builds exists for 1.13 extending the
life of Foreman on EL6 for that release and that release alone.
The Katello 3.2 release is the last release stream that will have
support for EL6. For Katello 3.3 and beyond, only EL7 releases will be made
available. We will be working on a strategy to help users migrate their EL6
installations to EL7 and please reach out to us if you have questions
regrading this.
Further, we recommend ALL new installs of 1.13 or 3.2 be done on an EL7
box.
To reiterate, Foreman 1.14 and Katello 3.2 will NOT be provided on EL6.
The 1.13 and 3.2 streams will continue to receive updates per our normal
support policy.
