How do you activate “Synced Content” as install media for certain “operating systems”?
For me it only works with “CentOS 7” as operating system, but with the same config it does not work for “CentOS 7.6.1810” as operating system. I don’t have a clue where to look for the problem.
How do you map a Content Source to a operating system and make the synced content available?
I have no experience with CentOS, but with RHEL you have to Sync the kickstart repository for that specific version and then add that to your content view.
After promoting the CV it should be accessible via “Synced Content”.
You really need to sync RHEL Kickstart repository, the original. CentOS will not work, even if it is really a repo with kickstart files it does not contain the important .treeinfo file with some details that Pulp/Katello needs to identify it as a “Kickstart” repository I think. @Justin_Sherrill should know better I might be wrong.
Now Justing will know better (or you can ask at the Pulp Project) but I think it’s because the missing .treeinfo file which is only on Red Hat CDN. Or maybe this information is stored in the subscription data, there are no subscriptions for CentOS.
This would be a nice feature to have indeed for CentOS.
It actually DOES work for Centos! …but only with Centos 7, not with Centos 7.6.
And Centos 7 is only a symlink to Centos 7.6.1810 on the mirror server, so the content of both is actually the same (until 7.7 will be published). So I’m pretty sure it’s not related to the content of the repo.
Again, my question is how does Foreman/Katello decide if a synced repo is valid for a certain OS version?
I just synced centos 7.6 on my instance and I am able to choose it as a synced content just fine. If you went to the repository details you should see -> “bootable:true”
Can you send me a screen shot of the “Distribution Information” in the repository details page for the 7.6
Can you also give me information regarding the values you chose for -> Lifecycle Env, Content View, Content Source, OS and arch when creating the host. Are you able to see the synced content if you chose “Library” and “Default Organization View”
Could be connected but I don’t think that is your issue because it worked fine on my test 3.10 instance.
Your distribution information looks correct. Give me the values for the the following boxes in your create hosts -> Lifecycle Env, Content View, Content Source, OS and arch when creating the host. Are you able to see the synced content if you chose “Library” and “Default Organization View”
You don’t have an os called “CentOS 7.6.1810” in your Infrastructure -> Operating System right?
Curious how that OS -> CentOS 7.6.1810 got generated. In my local instance I do not see this after syncing both Centos 7/7.6.
When we sync we create an OS entry from the distribution information provided in the treeinfo file. In your case the distribution information for both 7 and 7.6 point to the same thing (Centos 7). So to provision Centos 7.6 what you need to do is select OS -> Centos 7 and chose 7 or 7.6 repository from the synced content dropdown (you should see multiple repositories in the dropdown),