On 01/27/2018 08:42 PM, Chris Negus wrote:
----- Original Message -----
On Fri, Jan 26, 2018, at 9:53 AM, Chris Negus wrote:
I'm working on a procedure for installing RHEL Atomic on Azure. As part
of that, I want to install the WALinuxAgent RPM package, which is in the
rhel-7-server-extras-rpms repository. That repository is not enabled by
default. What I did was:
$ sudo atomic unlock
I don't think this step should be necessary?
Okay. Don't know why I thought I needed that.
$ sudo vi /etc/yum.repos.d/redhat.repo (and manually enabled the repo)
Hmm...would need to drill down into this one; I think we should be
enabling the extras repo but it might depend on your subscription state.
Unless you do something special in atomic, I think the extras repo is not
enabled by default in the redhat.repo file.
FWIW, my workflow usually looks like this (using a vanilla RHEL Server SKU):
# subscription-manager register
# subscription-manager repos --disable=*
# subscription-manager repos --enable rhel-7-server-rpms --enable
rhel-7-server-optional-rpms --enable rhel-7-server-extras-rpms
My questions is, is there a tool for enabling repos in Atomic (yum and
yum-config-manager aren't there) or is editing .repo files the way to do
that?
Just editing .repo files. I honestly never used yum-config-manager, but
I definitely run into people who have. It also seems to have been sort
of dropped with the dnf transition too? The thing that *does* trip
everything in the rpm-ostree model up is having RPMs that themselves
contain .repo files; the canonical example is epel-release. Personally I
just
rpm2cpio it or use Ansible to inject the GPG key and repo file, but down
the line I'd like to streamline things for the "RPMs that just have files in
/etc"
case.
Thanks. That's good information for something else I'm writing. For this
particular example, I'll just have them edit the redhat.repo file.
