Landscape standalone server 18.03 on Ubuntu 18.04: cannot sync pocket from demo (gpg certs missing?)
I'm trying to set up a Landscape standalone server on Ubuntu 18.04.1 LTS (for a demonstration at this point).
I have tried to set up the repository per these instructions: https://landscape.canonical.com/static/doc/user-guide/ch09.html
I get to the point where we sync the pocket that we've set up (the only deviation from the instructions provided is that I'm using bionic as the release and amd64 as the architecture).
Unfortunately, at this point, the sync doesn't succeed, as the result of the landscape-api get-activities --query id:<id returned from sync-mirror-pocket instruction> returns the following:
"ERROR: Condition '40976EAF437D05B5' not fulfilled for './lists/update-bionic_bionic_InRelease'.
Signatures in './lists/update-bionic_bionic_InRelease':
'3B4FE6ACC0B21F32' (signed 2018-04-26): missing pubkey
Error: Not enough signatures found for remote repository update-bionic (http://archive.ubuntu.com/ubuntu bionic)!
There have been errors!"
Initially, upon encountering this error, I downloaded the gpg key with the ID shown in the 'Condition' portion of message from the Ubuntu mirror, and installed it into the Landscape gpg key cache with a landscape-api import-gpg-key command (which succeeded). However, this did not solve the problem, and the condition persists.
Any help on this issue would be appreciated!
18.04 landscape
asked Jan 2 at 19:00
BigTruckManBigTruckMan
114
add a comment |
I'm trying to set up a Landscape standalone server on Ubuntu 18.04.1 LTS (for a demonstration at this point).
I have tried to set up the repository per these instructions: https://landscape.canonical.com/static/doc/user-guide/ch09.html
I get to the point where we sync the pocket that we've set up (the only deviation from the instructions provided is that I'm using bionic as the release and amd64 as the architecture).
Unfortunately, at this point, the sync doesn't succeed, as the result of the landscape-api get-activities --query id:<id returned from sync-mirror-pocket instruction> returns the following:
"ERROR: Condition '40976EAF437D05B5' not fulfilled for './lists/update-bionic_bionic_InRelease'.
Signatures in './lists/update-bionic_bionic_InRelease':
'3B4FE6ACC0B21F32' (signed 2018-04-26): missing pubkey
Error: Not enough signatures found for remote repository update-bionic (http://archive.ubuntu.com/ubuntu bionic)!
There have been errors!"
Initially, upon encountering this error, I downloaded the gpg key with the ID shown in the 'Condition' portion of message from the Ubuntu mirror, and installed it into the Landscape gpg key cache with a landscape-api import-gpg-key command (which succeeded). However, this did not solve the problem, and the condition persists.
Any help on this issue would be appreciated!
18.04 landscape
asked Jan 2 at 19:00
BigTruckManBigTruckMan
114
add a comment |
I'm trying to set up a Landscape standalone server on Ubuntu 18.04.1 LTS (for a demonstration at this point).
I have tried to set up the repository per these instructions: https://landscape.canonical.com/static/doc/user-guide/ch09.html
I get to the point where we sync the pocket that we've set up (the only deviation from the instructions provided is that I'm using bionic as the release and amd64 as the architecture).
Unfortunately, at this point, the sync doesn't succeed, as the result of the landscape-api get-activities --query id:<id returned from sync-mirror-pocket instruction> returns the following:
"ERROR: Condition '40976EAF437D05B5' not fulfilled for './lists/update-bionic_bionic_InRelease'.
Signatures in './lists/update-bionic_bionic_InRelease':
'3B4FE6ACC0B21F32' (signed 2018-04-26): missing pubkey
Error: Not enough signatures found for remote repository update-bionic (http://archive.ubuntu.com/ubuntu bionic)!
There have been errors!"
Initially, upon encountering this error, I downloaded the gpg key with the ID shown in the 'Condition' portion of message from the Ubuntu mirror, and installed it into the Landscape gpg key cache with a landscape-api import-gpg-key command (which succeeded). However, this did not solve the problem, and the condition persists.
Any help on this issue would be appreciated!
18.04 landscape
asked Jan 2 at 19:00
BigTruckManBigTruckMan
114
I'm trying to set up a Landscape standalone server on Ubuntu 18.04.1 LTS (for a demonstration at this point).
I have tried to set up the repository per these instructions: https://landscape.canonical.com/static/doc/user-guide/ch09.html
I get to the point where we sync the pocket that we've set up (the only deviation from the instructions provided is that I'm using bionic as the release and amd64 as the architecture).
Unfortunately, at this point, the sync doesn't succeed, as the result of the landscape-api get-activities --query id:<id returned from sync-mirror-pocket instruction> returns the following:
"ERROR: Condition '40976EAF437D05B5' not fulfilled for './lists/update-bionic_bionic_InRelease'.
Signatures in './lists/update-bionic_bionic_InRelease':
'3B4FE6ACC0B21F32' (signed 2018-04-26): missing pubkey
Error: Not enough signatures found for remote repository update-bionic (http://archive.ubuntu.com/ubuntu bionic)!
There have been errors!"
Initially, upon encountering this error, I downloaded the gpg key with the ID shown in the 'Condition' portion of message from the Ubuntu mirror, and installed it into the Landscape gpg key cache with a landscape-api import-gpg-key command (which succeeded). However, this did not solve the problem, and the condition persists.
Any help on this issue would be appreciated!
18.04 landscape
18.04 landscape
asked Jan 2 at 19:00
BigTruckManBigTruckMan
114
asked Jan 2 at 19:00
BigTruckManBigTruckMan
114
edited Jan 2 at 22:25
BigTruckMan
asked Jan 2 at 19:00
BigTruckManBigTruckMan
114
asked Jan 2 at 19:00
BigTruckManBigTruckMan
114
asked Jan 2 at 19:00
BigTruckManBigTruckMan
114
114
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I was able to solve my own problem.
Steps: first, use gpg to download the key with the missing public key ID (from above-'3B4FE6ACC0B21F32') from Ubuntu's key server (directions on verifying the identity of an Ubuntu image will have directions on that). Then, use gpg to export the key to a .pem file.
Next, import the key into the landscape API keychain, using landscape-api import-gpg-key. I named mine "ubuntu-bionic-public-key-2".
Finally, (and this part really needs to be added to the documentation that I originally referenced): do the following:
# landscape-api edit-pocket --mirror-gpg-key ubuntu-bionic-public-key-2 release bionic ubuntu
answered Jan 3 at 23:12
BigTruckManBigTruckMan
114
I'm glad you were able to figure it out. I've reported a bug (LP#1810793) to have the new mirror key added or documented.
– simpoir
Jan 7 at 14:23
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f1106362%2flandscape-standalone-server-18-03-on-ubuntu-18-04-cannot-sync-pocket-from-demo%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I was able to solve my own problem.
Steps: first, use gpg to download the key with the missing public key ID (from above-'3B4FE6ACC0B21F32') from Ubuntu's key server (directions on verifying the identity of an Ubuntu image will have directions on that). Then, use gpg to export the key to a .pem file.
Next, import the key into the landscape API keychain, using landscape-api import-gpg-key. I named mine "ubuntu-bionic-public-key-2".
Finally, (and this part really needs to be added to the documentation that I originally referenced): do the following:
# landscape-api edit-pocket --mirror-gpg-key ubuntu-bionic-public-key-2 release bionic ubuntu
answered Jan 3 at 23:12
BigTruckManBigTruckMan
114
I'm glad you were able to figure it out. I've reported a bug (LP#1810793) to have the new mirror key added or documented.
– simpoir
Jan 7 at 14:23
add a comment |
I was able to solve my own problem.
Steps: first, use gpg to download the key with the missing public key ID (from above-'3B4FE6ACC0B21F32') from Ubuntu's key server (directions on verifying the identity of an Ubuntu image will have directions on that). Then, use gpg to export the key to a .pem file.
Next, import the key into the landscape API keychain, using landscape-api import-gpg-key. I named mine "ubuntu-bionic-public-key-2".
Finally, (and this part really needs to be added to the documentation that I originally referenced): do the following:
# landscape-api edit-pocket --mirror-gpg-key ubuntu-bionic-public-key-2 release bionic ubuntu
answered Jan 3 at 23:12
BigTruckManBigTruckMan
114
I'm glad you were able to figure it out. I've reported a bug (LP#1810793) to have the new mirror key added or documented.
– simpoir
Jan 7 at 14:23
add a comment |
I was able to solve my own problem.
Steps: first, use gpg to download the key with the missing public key ID (from above-'3B4FE6ACC0B21F32') from Ubuntu's key server (directions on verifying the identity of an Ubuntu image will have directions on that). Then, use gpg to export the key to a .pem file.
Next, import the key into the landscape API keychain, using landscape-api import-gpg-key. I named mine "ubuntu-bionic-public-key-2".
Finally, (and this part really needs to be added to the documentation that I originally referenced): do the following:
# landscape-api edit-pocket --mirror-gpg-key ubuntu-bionic-public-key-2 release bionic ubuntu
answered Jan 3 at 23:12
BigTruckManBigTruckMan
114
I was able to solve my own problem.
Steps: first, use gpg to download the key with the missing public key ID (from above-'3B4FE6ACC0B21F32') from Ubuntu's key server (directions on verifying the identity of an Ubuntu image will have directions on that). Then, use gpg to export the key to a .pem file.
Next, import the key into the landscape API keychain, using landscape-api import-gpg-key. I named mine "ubuntu-bionic-public-key-2".
Finally, (and this part really needs to be added to the documentation that I originally referenced): do the following:
# landscape-api edit-pocket --mirror-gpg-key ubuntu-bionic-public-key-2 release bionic ubuntu
answered Jan 3 at 23:12
BigTruckManBigTruckMan
114
answered Jan 3 at 23:12
BigTruckManBigTruckMan
114
answered Jan 3 at 23:12
BigTruckManBigTruckMan
114
answered Jan 3 at 23:12
BigTruckManBigTruckMan
114
114
I'm glad you were able to figure it out. I've reported a bug (LP#1810793) to have the new mirror key added or documented.
– simpoir
Jan 7 at 14:23
add a comment |
I'm glad you were able to figure it out. I've reported a bug (LP#1810793) to have the new mirror key added or documented.
– simpoir
Jan 7 at 14:23
I'm glad you were able to figure it out. I've reported a bug (LP#1810793) to have the new mirror key added or documented.
– simpoir
Jan 7 at 14:23
I'm glad you were able to figure it out. I've reported a bug (LP#1810793) to have the new mirror key added or documented.
– simpoir
Jan 7 at 14:23
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1106362%2flandscape-standalone-server-18-03-on-ubuntu-18-04-cannot-sync-pocket-from-demo%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
