-
-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RHEL - rhui2-cds01.REGION.aws.ce.redhat.com not resolvable #93
Comments
I ran into something similar today, and the cause was a missing |
Ah, it does have something to do with AWS? These settings are AWS defaults for RHEL. I know this may sound crazy, but I have RHEL7 VMs that are not in AWS :p |
I know this may sound crazy, but RHEL-on-AWS should detect as a different OS from RHEL-not-on-AWS. (winky-grin) |
Agreed! I am a bit curious... wouldn't a variable need to be formatted like ~tommy |
I agree with @TJM, this is a little odd. I'm going to do some digging into it to see why it's happening. |
The module hiera config file just uses os.family and os.release* to determine which default repos to include. Obviously trying to figure out if a node is in ec2 in hiera isn't simple, but I don't think assuming it is and laying down repos which don't work isn't the right way to go. Obviously trying to manage the default repos on RHEL won't work unless the node registered through RHSM. @pillarsdotnet could you share any background on the changes made in #75 and #76 ? |
For me, this was resolived by installing the rh-amazon-rhui-client rpm. Because I could not do anything with dnf (yum), I could not install it with "dnf install rh-amazon-rhui-client". I had to go to a working server, run "dnf download rh-amazon-rhui-client", which downloaded the file rh-amazon-rhui-client-4.0.14-1.el8.noarch.rpm. I copied that file to the broken server and ran "rpm -Uvh rh-amazon-rhui-client-4.0.14-1.el8.noarch.rpm" to install it. Then, when I ran "dnf update", it reconfigured itself and began working. |
Sorry; at the time I wrote those patches, I was working AWS-only. But "trying to figure out if a node is in ec2 in hiera" is pretty simple. All you need is a fact that resolves one way for ec2 and a different way for non-ec2. I've written such a fact in a proprietary setting. Here's what the top-level looks like:
|
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
include ::yum
What are you seeing
Errors during yum operations:
What behaviour did you expect instead
I think the defaults provided through module data should work as a general rule. Perhaps, if they are "Amazon" specific defaults, we should add a layer to the hiera.yaml to detect the amazon-ness and include these defaults then? or come up with a generic default, and only override the "mirrorlist"
Output log
Relevant information included above.
Any additional information you'd like to impart
This relates to PR #75 and Issue #76 ... Perhaps @pillarsdotnet can shed some light on how it is supposed to work.
The text was updated successfully, but these errors were encountered: