I am trying to figure out what process or trigger is responsible to auto
update build complete status for any server built via unattended
installation. Since, even after the OS is installed, I can still see
"Cancel Build" activated in the UI.
If it's failing, check first in Foreman's logs
(/var/log/foreman/production.log) to see if the request is even making
it to Foreman, or if it is and it's failing.
···
On 18/09/15 13:07, nitin wrote:
> Hey Guys,
>
> I am trying to figure out what process or trigger is responsible to auto
> update build complete status for any server built via unattended
> installation. Since, even after the OS is installed, I can still see
> "Cancel Build" activated in the UI.
>
> Does anyone have idea about this?
Thanks Dominic, That was much useful help. wget command is in there in the
finish script, which resolves to the host, but somehow it is not getting
applied. I've put the wget command in %post now to make it work.
Nitin
···
On Friday, September 18, 2015 at 6:24:22 AM UTC-7, Dominic Cleal wrote:
>
> On 18/09/15 13:07, nitin wrote:
> > Hey Guys,
> >
> > I am trying to figure out what process or trigger is responsible to auto
> > update build complete status for any server built via unattended
> > installation. Since, even after the OS is installed, I can still see
> > "Cancel Build" activated in the UI.
> >
> > Does anyone have idea about this?
>
> There's a wget command at the end of our finish/%post sections which
> requests /unattended/built on Foreman.
>
>
> https://github.com/theforeman/community-templates/blob/develop/preseed/finish.erb#L63
> for example.
>
> If it's failing, check first in Foreman's logs
> (/var/log/foreman/production.log) to see if the request is even making
> it to Foreman, or if it is and it's failing.
>
> --
> Dominic Cleal
> dom...@cleal.org
>
