Skip to content
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

Unable to download ubuntu bzr updates on clair 1.0 #169

Closed
ghost opened this issue May 6, 2016 · 4 comments
Closed

Unable to download ubuntu bzr updates on clair 1.0 #169

ghost opened this issue May 6, 2016 · 4 comments
Labels
kind/question something that couldn't be answered in the docs

Comments

@ghost
Copy link

ghost commented May 6, 2016

2016-05-06 13:07:12.421066 E | updater/fetchers/ubuntu: could not branch Ubuntu repository: exit status 3. output: You have not informed bzr of your Launchpad ID, and you must do this to
write to Launchpad or access private data. See "bzr help launchpad-login".
bzr: ERROR: http://bazaar.launchpad.net/~ubuntu-security/ubuntu-cve-tracker/master/.bzr/repository/packs/2e9c085340ade7642e29c378525be05e.pack is redirected to https://launchpad.net
2016-05-06 13:07:12.421102 E | updater: an error occured when fetching update 'Ubuntu': could not download requested ressource.

@Quentin-M Quentin-M added component/updater kind/question something that couldn't be answered in the docs labels May 12, 2016
@Quentin-M
Copy link
Contributor

Hi,

Can you confirm that you can run bzr branch lp:ubuntu-cve-tracker in your environment?

@jlk
Copy link

jlk commented May 19, 2016

I'm running into similar - this is with v1.1.0 of the clair container from docker hub:

2016-05-19 23:49:01.438776 I | updater: updating vulnerabilities
2016-05-19 23:49:01.438851 I | updater: fetching vulnerability updates
2016-05-19 23:49:01.438896 I | updater/fetchers/ubuntu: fetching Ubuntu vulnerabilities
2016-05-19 23:49:01.439005 I | updater/fetchers/debian: fetching Debian vulnerabilities
2016-05-19 23:49:01.439066 I | updater/fetchers/rhel: fetching Red Hat vulnerabilities
2016-05-19 23:49:09.906782 E | updater/fetchers/ubuntu: could not branch Ubuntu repository: exit status 3. output: You have not informed bzr of your Launchpad ID, and you must do this to
write to Launchpad or access private data.  See "bzr help launchpad-login".
bzr: ERROR: Cannot lock LockDir(file:///tmp/ubuntu-cve-tracker175949639/repository/.bzr/branch-lock): lock was renamed into place, but now is missing!
2016-05-19 23:49:09.906837 E | updater: an error occured when fetching update 'Ubuntu': could not download requested resource.
2016-05-19 23:49:18.605314 I | updater: adding metadata to vulnerabilities
2016-05-19 23:50:53.813978 I | updater: update finished
2016-05-19 23:50:53.820616 I | updater: updating vulnerabilities
2016-05-19 23:50:53.820663 I | updater: fetching vulnerability updates
2016-05-19 23:50:53.820708 I | updater/fetchers/debian: fetching Debian vulnerabilities
2016-05-19 23:50:53.820750 I | updater/fetchers/rhel: fetching Red Hat vulnerabilities
2016-05-19 23:50:53.820844 I | updater/fetchers/ubuntu: fetching Ubuntu vulnerabilities
2016-05-19 23:50:53.883735 E | updater/fetchers/ubuntu: could not pull Ubuntu repository: exit status 3. output: bzr: ERROR: Not a branch: "/tmp/ubuntu-cve-tracker175949639/repository/".
2016-05-19 23:50:53.883776 E | updater: an error occured when fetching update 'Ubuntu': could not download requested resource.
2016-05-19 23:50:59.365975 I | updater: adding metadata to vulnerabilities
2016-05-19 23:51:34.911999 I | updater: update finished

The updater then loops about once a minute. I am able to run bzr branch manually in the container:

root@9d18b7b34086:/go/src/github.com/coreos/clair# bzr branch lp:ubuntu-cve-tracker
You have not informed bzr of your Launchpad ID, and you must do this to
write to Launchpad or access private data.  See "bzr help launchpad-login".
Branched 11055 revisions.

@Quentin-M
Copy link
Contributor

Quentin-M commented May 20, 2016

Hi,

Thanks for the report. I'll take a look. I will look into it, it really looks like a bzr bug to me.

However, you mentioned using the Clair container image from the Docker Hub. We do not maintain an image on this registry. Could you please tell me which image exactly are you using from there?

Linking #176.

@jlk
Copy link

jlk commented May 20, 2016

Whoops my bad - I pull it from Quay sorry :)

I'll do further testing over the weekend as well...I had (have?) this setup working in prod...just noticed the issue when I was spinning up a new service in dev w/ Docker for Mac.

Quentin-M added a commit to Quentin-M/clair that referenced this issue May 25, 2016
By deleting an Ubuntu repository that may be in a bad state,
Clair will eventually be able to perform the update, instead of retrying
naively.

Fixes quay#169
Quentin-M added a commit to Quentin-M/clair that referenced this issue Jun 9, 2016
By deleting an Ubuntu repository that may be in a bad state,
Clair will eventually be able to perform the update, instead of retrying naively.

Fixes quay#169
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question something that couldn't be answered in the docs
Development

No branches or pull requests

2 participants