I'm new to Foreman, so I apologize in advance if I'm missing something
clearly obvious.
I've copied the contents of the RHEL7 iso to a webserver and have that URL
defined as the installation media for my RHEL7 operating system. I'm able
to provision a bare metal machine using this URL and foreman, and I can log
in via ssh using the credentials I specified with the foreman-installer.
Provisioning is "working" in a sense that the bare metal machine is spun up
as with vanilla RHEL7, but that's where the happy face turns upside down.
I'm not able to install any packages without manually handling the RedHat
subscription management stuff. When looking at the deployment process in
the Foreman UI, the neutron controller is consistently getting stuck at
60%, and there are no obvious logs on the newly launched machine to
indicate where the problem actually lies. I do notice there are no yum
repos defined, and I suspect that is part of my problem. (How can we
install puppet if there are no repos?) I also notice that none of the
RedHat registration stuff is happening, so I can't even manually install
packages without first doing the manual RedHat registration. Other than
production.log on the foreman server, is there somewhere else that may be
able to tell me why the deployment of the controller is consistently
stalling? Do I need to add a puppet package to the install media? I'm
lost as to how to proceed.
I did notice in the provisioning template, there is a reference to a
snippet called "redhat_register" that then refers to variables that seem
like they may be useful at some point: subscription_manager_username
and subscription_manager_password. Where can I find where those are set,
or how can I define them? I suspect that may be the "phase 2" solution,
since I don't even see logs of any attempts to run RedHat subscribe at this
point.
Many thanks for taking the time to read this.
Cheers,
Bill
Hello,
you have to use subscription manager. rhel-osp-installer asks you for
credentials during installation. The it creates parameters in Foreman that are
used in redhat_register snippet you've mentioned.
Please use staypuft rdo-list for questions. You can find all communication
channels here [1]
[1] https://github.com/theforeman/staypuft#contributing
Hope this helps
···
--
Marek
On Wednesday 15 of October 2014 18:03:13 Bill Bartlett wrote:
I’m new to Foreman, so I apologize in advance if I’m missing something
clearly obvious.
I’ve copied the contents of the RHEL7 iso to a webserver and have that URL
defined as the installation media for my RHEL7 operating system. I’m able
to provision a bare metal machine using this URL and foreman, and I can log
in via ssh using the credentials I specified with the foreman-installer.
Provisioning is “working” in a sense that the bare metal machine is spun up
as with vanilla RHEL7, but that’s where the happy face turns upside down.
I’m not able to install any packages without manually handling the RedHat
subscription management stuff. When looking at the deployment process in
the Foreman UI, the neutron controller is consistently getting stuck at
60%, and there are no obvious logs on the newly launched machine to
indicate where the problem actually lies. I do notice there are no yum
repos defined, and I suspect that is part of my problem. (How can we
install puppet if there are no repos?) I also notice that none of the
RedHat registration stuff is happening, so I can’t even manually install
packages without first doing the manual RedHat registration. Other than
production.log on the foreman server, is there somewhere else that may be
able to tell me why the deployment of the controller is consistently
stalling? Do I need to add a puppet package to the install media? I’m
lost as to how to proceed.
I did notice in the provisioning template, there is a reference to a
snippet called “redhat_register” that then refers to variables that seem
like they may be useful at some point: subscription_manager_username
and subscription_manager_password. Where can I find where those are set,
or how can I define them? I suspect that may be the “phase 2” solution,
since I don’t even see logs of any attempts to run RedHat subscribe at this
point.
Many thanks for taking the time to read this.
Cheers,
Bill
Thanks, Marek. I made significant progress last night figuring out how to
get parameters working for redhat_register. I'll go over to the rdo list
as you suggest for further help.
···
On Thursday, October 16, 2014 1:54:27 AM UTC-7, Marek Hulan wrote:
>
> Hello,
>
> you have to use subscription manager. rhel-osp-installer asks you for
> credentials during installation. The it creates parameters in Foreman that
> are
> used in redhat_register snippet you've mentioned.
>
> Please use staypuft rdo-list for questions. You can find all communication
> channels here [1]
>
> [1] https://github.com/theforeman/staypuft#contributing
>
> Hope this helps
>
> --
> Marek
>
> On Wednesday 15 of October 2014 18:03:13 Bill Bartlett wrote:
> > I'm new to Foreman, so I apologize in advance if I'm missing something
> > clearly obvious.
> >
> > I've copied the contents of the RHEL7 iso to a webserver and have that
> URL
> > defined as the installation media for my RHEL7 operating system. I'm
> able
> > to provision a bare metal machine using this URL and foreman, and I can
> log
> > in via ssh using the credentials I specified with the foreman-installer.
> >
> > Provisioning is "working" in a sense that the bare metal machine is spun
> up
> > as with vanilla RHEL7, but that's where the happy face turns upside
> down.
> > I'm not able to install any packages without manually handling the
> RedHat
> > subscription management stuff. When looking at the deployment process
> in
> > the Foreman UI, the neutron controller is consistently getting stuck at
> > 60%, and there are no obvious logs on the newly launched machine to
> > indicate where the problem actually lies. I do notice there are no yum
> > repos defined, and I suspect that is part of my problem. (How can we
> > install puppet if there are no repos?) I also notice that none of the
> > RedHat registration stuff is happening, so I can't even manually install
> > packages without first doing the manual RedHat registration. Other than
> > production.log on the foreman server, is there somewhere else that may
> be
> > able to tell me why the deployment of the controller is consistently
> > stalling? Do I need to add a puppet package to the install media? I'm
> > lost as to how to proceed.
> >
> > I did notice in the provisioning template, there is a reference to a
> > snippet called "redhat_register" that then refers to variables that seem
> > like they may be useful at some point: subscription_manager_username
> > and subscription_manager_password. Where can I find where those are
> set,
> > or how can I define them? I suspect that may be the "phase 2" solution,
> > since I don't even see logs of any attempts to run RedHat subscribe at
> this
> > point.
> >
> > Many thanks for taking the time to read this.
> >
> > Cheers,
> > Bill
>
>
