trying to install chef-client package via local yum repohttpd-devel requires outdated version of glibc-common...
Unknown code in script
Is Diceware more secure than a long passphrase?
Can someone publish a story that happened to you?
Find the identical rows in a matrix
Does the damage from the Absorb Elements spell apply to your next attack, or to your first attack on your next turn?
How can I practically buy stocks?
"The cow" OR "a cow" OR "cows" in this context
Can a stored procedure reference the database in which it is stored?
Multiple options vs single option UI
Co-worker works way more than he should
What is purpose of DB Browser(dbbrowser.aspx) under admin tool?
A faster way to compute the largest prime factor
Combinatorics problem, right solution?
What does "function" actually mean in music?
Why did Rep. Omar conclude her criticism of US troops with the phrase "NotTodaySatan"?
What is the term for a person whose job is to place products on shelves in stores?
"Whatever a Russian does, they end up making the Kalashnikov gun"? Are there any similar proverbs in English?
A Note on N!
How do I produce this symbol: Ϟ in pdfLaTeX?
Island of Knights, Knaves and Spies
What to do with someone that cheated their way through university and a PhD program?
How long after the last departure shall the airport stay open for an emergency return?
Double-nominative constructions and “von”
Contradiction proof for inequality of P and NP?
trying to install chef-client package via local yum repo
httpd-devel requires outdated version of glibc-common on CentOS 6.3What is a good distribution to use that is similar to Amazon LinuxHow to force rpm and yum to fail if a GPG signature is missing or cannot otherwise be verified?yum remove is not idempotentUnable to “yum install” RPM package from local repository (Oracle Linux)Unable to install packages from local repo - RHEL 7.3yum install and update fail - GPG keys listed for the “CentOS-7 - Updates” repository are already installed but they are not correctIssue with elrepo-kernel: packages are not availableyum install multiple packages requiring all for successcannot offline install vnc server on CentOS 7
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am trying to make chef-11.16.4-1.el6.x86_64.rpm available to our servers via a local yum repo that we've built.
it is not available in RHEL Repos, so i had to manually download and save it in our repo.
so here is what i did on yum repo server:
1. cd /packages/rhel65-base/; wget https://opscode-omnibus-packages.s3.amazonaws.com/el/6/x86_64/chef-11.16.4-1.el6.x86_64.rpm
2. createrepo /packages/rhel65-base/
Yum client was able to see the new package available:
[user1@testserver01 ~]$ yum list chef
Loaded plugins: amazon-id, rhui-lb, security
Installed Packages
chef.x86_64 11.16.0-1.el6 installed
Available Packages
chef.x86_64 11.16.4-1.el6 local-rhel65-base
But when trying to install the latest package of chef, it ends with below error:
warning: rpmts_HdrFromFdno: Header V4 DSA/SHA1 Signature, key ID 83ef826a: NOKEY
Public key for chef-11.16.4-1.el6.x86_64.rpm is not installed
Assuming that the chef rpm has not been signed, i tried to sign it myself by following https://iuscommunity.org/pages/CreatingAGPGKeyandSigningRPMs.html but still couldn't get it working.
Some useful info i can find in Chef's website is the SHA1 checksum value of this package.
Anyone got ideas/suggestions to solve this issue? thanks!
yum rpm gpg chef
bumped to the homepage by Community♦ 36 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am trying to make chef-11.16.4-1.el6.x86_64.rpm available to our servers via a local yum repo that we've built.
it is not available in RHEL Repos, so i had to manually download and save it in our repo.
so here is what i did on yum repo server:
1. cd /packages/rhel65-base/; wget https://opscode-omnibus-packages.s3.amazonaws.com/el/6/x86_64/chef-11.16.4-1.el6.x86_64.rpm
2. createrepo /packages/rhel65-base/
Yum client was able to see the new package available:
[user1@testserver01 ~]$ yum list chef
Loaded plugins: amazon-id, rhui-lb, security
Installed Packages
chef.x86_64 11.16.0-1.el6 installed
Available Packages
chef.x86_64 11.16.4-1.el6 local-rhel65-base
But when trying to install the latest package of chef, it ends with below error:
warning: rpmts_HdrFromFdno: Header V4 DSA/SHA1 Signature, key ID 83ef826a: NOKEY
Public key for chef-11.16.4-1.el6.x86_64.rpm is not installed
Assuming that the chef rpm has not been signed, i tried to sign it myself by following https://iuscommunity.org/pages/CreatingAGPGKeyandSigningRPMs.html but still couldn't get it working.
Some useful info i can find in Chef's website is the SHA1 checksum value of this package.
Anyone got ideas/suggestions to solve this issue? thanks!
yum rpm gpg chef
bumped to the homepage by Community♦ 36 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am trying to make chef-11.16.4-1.el6.x86_64.rpm available to our servers via a local yum repo that we've built.
it is not available in RHEL Repos, so i had to manually download and save it in our repo.
so here is what i did on yum repo server:
1. cd /packages/rhel65-base/; wget https://opscode-omnibus-packages.s3.amazonaws.com/el/6/x86_64/chef-11.16.4-1.el6.x86_64.rpm
2. createrepo /packages/rhel65-base/
Yum client was able to see the new package available:
[user1@testserver01 ~]$ yum list chef
Loaded plugins: amazon-id, rhui-lb, security
Installed Packages
chef.x86_64 11.16.0-1.el6 installed
Available Packages
chef.x86_64 11.16.4-1.el6 local-rhel65-base
But when trying to install the latest package of chef, it ends with below error:
warning: rpmts_HdrFromFdno: Header V4 DSA/SHA1 Signature, key ID 83ef826a: NOKEY
Public key for chef-11.16.4-1.el6.x86_64.rpm is not installed
Assuming that the chef rpm has not been signed, i tried to sign it myself by following https://iuscommunity.org/pages/CreatingAGPGKeyandSigningRPMs.html but still couldn't get it working.
Some useful info i can find in Chef's website is the SHA1 checksum value of this package.
Anyone got ideas/suggestions to solve this issue? thanks!
yum rpm gpg chef
I am trying to make chef-11.16.4-1.el6.x86_64.rpm available to our servers via a local yum repo that we've built.
it is not available in RHEL Repos, so i had to manually download and save it in our repo.
so here is what i did on yum repo server:
1. cd /packages/rhel65-base/; wget https://opscode-omnibus-packages.s3.amazonaws.com/el/6/x86_64/chef-11.16.4-1.el6.x86_64.rpm
2. createrepo /packages/rhel65-base/
Yum client was able to see the new package available:
[user1@testserver01 ~]$ yum list chef
Loaded plugins: amazon-id, rhui-lb, security
Installed Packages
chef.x86_64 11.16.0-1.el6 installed
Available Packages
chef.x86_64 11.16.4-1.el6 local-rhel65-base
But when trying to install the latest package of chef, it ends with below error:
warning: rpmts_HdrFromFdno: Header V4 DSA/SHA1 Signature, key ID 83ef826a: NOKEY
Public key for chef-11.16.4-1.el6.x86_64.rpm is not installed
Assuming that the chef rpm has not been signed, i tried to sign it myself by following https://iuscommunity.org/pages/CreatingAGPGKeyandSigningRPMs.html but still couldn't get it working.
Some useful info i can find in Chef's website is the SHA1 checksum value of this package.
Anyone got ideas/suggestions to solve this issue? thanks!
yum rpm gpg chef
yum rpm gpg chef
asked Aug 11 '15 at 15:08
takitaki
47110
47110
bumped to the homepage by Community♦ 36 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 36 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
If the package isn't signed, the simplest solution is probably yum --nogpgcheck install chef. If you have a local repository, you can set:
gpgcheck=no
In the corresponding .repo file.
yes, it works with nogpgcheck option, but i am looking for help with installing the rpm with gpg enabled. thanks
– taki
Aug 11 '15 at 15:39
2
That wasn't clear from your question. Can you update your question with details of the steps you went through to (a) sign the package and (b) import the signing key on your systems? And include any errors you get, or places where the behavior you see is different from the expected behavior.
– larsks
Aug 11 '15 at 15:46
add a comment |
The problem here is that you haven't configured your server to accept the key that signed the package as a valid GPG key for this repo.
The easiest solution is of course to run yum with nogpgcheck, though it's obviously also less secure. But if you've downloaded the package and verified it, and are keeping it in a place where it shouldn't be possible to tamper with it, it may be acceptable.
If this isn't acceptable, you need to fetch the public part of the key that was used to sign the package and place it on the server where you're trying to install the package. You should be able to do it by simply copying the key there and running rpm -i /path/to/RPM-GPG-KEY-REPONAME.
The key should normally be placed in /etc/pki/rpm-gpg/RPM-GPG-KEY-REPONAME. Also check the repo file for your repo in /etc/yum.repos.d so that it contains the following lines:
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-REPONAME
gpgcheck=1
add a comment |
This is an old question but still valuable to answer I believe to prevent misleading information. The package is signed as you can see from the message :
Public key for chef-11.16.4-1.el6.x86_64.rpm is not installed
However the key isn't installed... I tried to search for this package key but couldn't find an url for it (This is what led me here in fact). When found/validated you can import it via:
rpm --import <url>
The solution from @larsks disabled the checking of the gpg key...
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f222544%2ftrying-to-install-chef-client-package-via-local-yum-repo%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
If the package isn't signed, the simplest solution is probably yum --nogpgcheck install chef. If you have a local repository, you can set:
gpgcheck=no
In the corresponding .repo file.
yes, it works with nogpgcheck option, but i am looking for help with installing the rpm with gpg enabled. thanks
– taki
Aug 11 '15 at 15:39
2
That wasn't clear from your question. Can you update your question with details of the steps you went through to (a) sign the package and (b) import the signing key on your systems? And include any errors you get, or places where the behavior you see is different from the expected behavior.
– larsks
Aug 11 '15 at 15:46
add a comment |
If the package isn't signed, the simplest solution is probably yum --nogpgcheck install chef. If you have a local repository, you can set:
gpgcheck=no
In the corresponding .repo file.
yes, it works with nogpgcheck option, but i am looking for help with installing the rpm with gpg enabled. thanks
– taki
Aug 11 '15 at 15:39
2
That wasn't clear from your question. Can you update your question with details of the steps you went through to (a) sign the package and (b) import the signing key on your systems? And include any errors you get, or places where the behavior you see is different from the expected behavior.
– larsks
Aug 11 '15 at 15:46
add a comment |
If the package isn't signed, the simplest solution is probably yum --nogpgcheck install chef. If you have a local repository, you can set:
gpgcheck=no
In the corresponding .repo file.
If the package isn't signed, the simplest solution is probably yum --nogpgcheck install chef. If you have a local repository, you can set:
gpgcheck=no
In the corresponding .repo file.
answered Aug 11 '15 at 15:31
larskslarsks
11.7k33042
11.7k33042
yes, it works with nogpgcheck option, but i am looking for help with installing the rpm with gpg enabled. thanks
– taki
Aug 11 '15 at 15:39
2
That wasn't clear from your question. Can you update your question with details of the steps you went through to (a) sign the package and (b) import the signing key on your systems? And include any errors you get, or places where the behavior you see is different from the expected behavior.
– larsks
Aug 11 '15 at 15:46
add a comment |
yes, it works with nogpgcheck option, but i am looking for help with installing the rpm with gpg enabled. thanks
– taki
Aug 11 '15 at 15:39
2
That wasn't clear from your question. Can you update your question with details of the steps you went through to (a) sign the package and (b) import the signing key on your systems? And include any errors you get, or places where the behavior you see is different from the expected behavior.
– larsks
Aug 11 '15 at 15:46
yes, it works with nogpgcheck option, but i am looking for help with installing the rpm with gpg enabled. thanks
– taki
Aug 11 '15 at 15:39
yes, it works with nogpgcheck option, but i am looking for help with installing the rpm with gpg enabled. thanks
– taki
Aug 11 '15 at 15:39
2
2
That wasn't clear from your question. Can you update your question with details of the steps you went through to (a) sign the package and (b) import the signing key on your systems? And include any errors you get, or places where the behavior you see is different from the expected behavior.
– larsks
Aug 11 '15 at 15:46
That wasn't clear from your question. Can you update your question with details of the steps you went through to (a) sign the package and (b) import the signing key on your systems? And include any errors you get, or places where the behavior you see is different from the expected behavior.
– larsks
Aug 11 '15 at 15:46
add a comment |
The problem here is that you haven't configured your server to accept the key that signed the package as a valid GPG key for this repo.
The easiest solution is of course to run yum with nogpgcheck, though it's obviously also less secure. But if you've downloaded the package and verified it, and are keeping it in a place where it shouldn't be possible to tamper with it, it may be acceptable.
If this isn't acceptable, you need to fetch the public part of the key that was used to sign the package and place it on the server where you're trying to install the package. You should be able to do it by simply copying the key there and running rpm -i /path/to/RPM-GPG-KEY-REPONAME.
The key should normally be placed in /etc/pki/rpm-gpg/RPM-GPG-KEY-REPONAME. Also check the repo file for your repo in /etc/yum.repos.d so that it contains the following lines:
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-REPONAME
gpgcheck=1
add a comment |
The problem here is that you haven't configured your server to accept the key that signed the package as a valid GPG key for this repo.
The easiest solution is of course to run yum with nogpgcheck, though it's obviously also less secure. But if you've downloaded the package and verified it, and are keeping it in a place where it shouldn't be possible to tamper with it, it may be acceptable.
If this isn't acceptable, you need to fetch the public part of the key that was used to sign the package and place it on the server where you're trying to install the package. You should be able to do it by simply copying the key there and running rpm -i /path/to/RPM-GPG-KEY-REPONAME.
The key should normally be placed in /etc/pki/rpm-gpg/RPM-GPG-KEY-REPONAME. Also check the repo file for your repo in /etc/yum.repos.d so that it contains the following lines:
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-REPONAME
gpgcheck=1
add a comment |
The problem here is that you haven't configured your server to accept the key that signed the package as a valid GPG key for this repo.
The easiest solution is of course to run yum with nogpgcheck, though it's obviously also less secure. But if you've downloaded the package and verified it, and are keeping it in a place where it shouldn't be possible to tamper with it, it may be acceptable.
If this isn't acceptable, you need to fetch the public part of the key that was used to sign the package and place it on the server where you're trying to install the package. You should be able to do it by simply copying the key there and running rpm -i /path/to/RPM-GPG-KEY-REPONAME.
The key should normally be placed in /etc/pki/rpm-gpg/RPM-GPG-KEY-REPONAME. Also check the repo file for your repo in /etc/yum.repos.d so that it contains the following lines:
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-REPONAME
gpgcheck=1
The problem here is that you haven't configured your server to accept the key that signed the package as a valid GPG key for this repo.
The easiest solution is of course to run yum with nogpgcheck, though it's obviously also less secure. But if you've downloaded the package and verified it, and are keeping it in a place where it shouldn't be possible to tamper with it, it may be acceptable.
If this isn't acceptable, you need to fetch the public part of the key that was used to sign the package and place it on the server where you're trying to install the package. You should be able to do it by simply copying the key there and running rpm -i /path/to/RPM-GPG-KEY-REPONAME.
The key should normally be placed in /etc/pki/rpm-gpg/RPM-GPG-KEY-REPONAME. Also check the repo file for your repo in /etc/yum.repos.d so that it contains the following lines:
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-REPONAME
gpgcheck=1
answered Aug 12 '15 at 14:13
Jenny DJenny D
10.8k22847
10.8k22847
add a comment |
add a comment |
This is an old question but still valuable to answer I believe to prevent misleading information. The package is signed as you can see from the message :
Public key for chef-11.16.4-1.el6.x86_64.rpm is not installed
However the key isn't installed... I tried to search for this package key but couldn't find an url for it (This is what led me here in fact). When found/validated you can import it via:
rpm --import <url>
The solution from @larsks disabled the checking of the gpg key...
add a comment |
This is an old question but still valuable to answer I believe to prevent misleading information. The package is signed as you can see from the message :
Public key for chef-11.16.4-1.el6.x86_64.rpm is not installed
However the key isn't installed... I tried to search for this package key but couldn't find an url for it (This is what led me here in fact). When found/validated you can import it via:
rpm --import <url>
The solution from @larsks disabled the checking of the gpg key...
add a comment |
This is an old question but still valuable to answer I believe to prevent misleading information. The package is signed as you can see from the message :
Public key for chef-11.16.4-1.el6.x86_64.rpm is not installed
However the key isn't installed... I tried to search for this package key but couldn't find an url for it (This is what led me here in fact). When found/validated you can import it via:
rpm --import <url>
The solution from @larsks disabled the checking of the gpg key...
This is an old question but still valuable to answer I believe to prevent misleading information. The package is signed as you can see from the message :
Public key for chef-11.16.4-1.el6.x86_64.rpm is not installed
However the key isn't installed... I tried to search for this package key but couldn't find an url for it (This is what led me here in fact). When found/validated you can import it via:
rpm --import <url>
The solution from @larsks disabled the checking of the gpg key...
answered Jul 25 '16 at 14:13
ROunofFROunofF
1011
1011
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f222544%2ftrying-to-install-chef-client-package-via-local-yum-repo%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown