[Katello 2.4] Can not save Operating System Media when updating a host group

Support
1

I am experiencing some really really strange behavior. Basically, I have
created an installation media source for CentOS 6.7 and added it as an
operating sytem, and then given it access to that media.

When I try to edit a host group to get it to use that operating system
media as an installation source, it doesn't work.

Here is what I do (screenshots attached)

1)Go to Operating system tab on a hostgroup. Choose an architecture,
operating sytem, and media.

Click Submit to save
Now go back in and edit the hostgroup and the dropdown menu has been
replaced with something I can no longer edit at all… Plus it's not
pointing at the media that I chose in the last screen (which was a full
path to centos installation directory). Its now pointing to a content view
that I definitely did not choose.

If I choose a different OS from the content box I get the ability to choose
the media again.

So I choose the media I want :

But when I click submit again and re-load the page, it has once again
decided to remove the "Prod" OS install disk I pointed to and instead point
back to some random view

Does anyone know why this is happening or how I can fix it ?

Auto Generated Inline Image 1 (11.8 KB)

2

Something that I find even more confusing is why those things show up on my
menu in the first place. I couldn't find anything in the manual about this
either.

When I go to the operating system page, you can see the Prod installation
media pointing to a legitimate installation source. You can also see those
'fake' installation media that were somehow automatically created when I
published some views.

What I can't find information on anywhere is why those were created at
all… I noticed in earlier test that if I pointed to them as installation
paths, it failed because they didn't have vmlinuz and initrd in their
paths? Why would katello sync a installation repo, strip all the file
except repo files, and then claim it is a valid installation source?

Also, why would it override the actual legitimate installation source I
manually entered on the hostgroup page with one of these fake installation
sources it created when I published the content views?

Also… Why would it claim it was successfully grabbing the boot sources
and then put zero byte files on my hard drive when I provision a host?

FYI, the screenshot below is from a proxy.

I need to know how to set this up properly. I have 2 networks : prod, and
dev. The management host is in dev, a tftp/template proxy in prod. I have
installation sources in both prod and dev, so I added the images and named
the ones in prod "Prod".

So when I provision a host in prod, is it the foreman proxy in prod that
tries to contact the installation source and grab the vmlinuz file, or is
it my main katello machine that will try to grab it and then transfer it
somehow to the proxy?

The manual is really vague on all these details and it's getting hard to
troubleshoot why I can't choose the disk I want, and why the disks that it
does decide to put there are zero bytes.

Auto Generated Inline Image 1 (4.32 KB)

3

Screenshot of OS media page attached :

Auto Generated Inline Image 1 (13.6 KB)

4

Katello is not my strongest area, so hopefully on of the devs will reply on
that side. However, in general, a zero-byte file just means the proxy
couldn;t get the file from the URL. It's a side effect of the options we
use to wget for downloading files - it runs in append mode, so it starts
with a zero-size file and adds to it as it receives data.

Short version - the URL the proxy is using isn't working - but we'll
probably need someone with more katello experience than I to answer the
why of it.

Greg

··· On 15 January 2016 at 01:18, Nathan Peters wrote:

Also… Why would it claim it was successfully grabbing the boot sources
and then put zero byte files on my hard drive when I provision a host?