Project

Profile

Help

Task #6847

Control of repo existance

Added by Mark Zaslavskiy almost 6 years ago. Updated over 5 years ago.

Status:
Won't fix
Priority:
Low
Assignee:
Alexander Kaluzhny
Category:
mdbci features
Sprint/Milestone:
Start date:
26.02.2016
Due date:
% Done:

0%

Estimated time:
Target branch:
Test scenario:

Description

думаю если не ставится Maxscale, то тут надо просто выдавать ошибку. А
ключик --skip-broken и --disablerepo=maxscale при установке net-tools (и
всего, кроме maxscale) не поможет?

- add check for repo existance
- add keys for skip bad repo during net-tools install

History

#1 Updated by Alexander Kaluzhny over 5 years ago

  • Status changed from New to Active / In progress

#2 Updated by Mark Zaslavskiy over 5 years ago

  • Status changed from Active / In progress to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy

#3 Updated by Mark Zaslavskiy over 5 years ago

  • Status changed from Review to Active / In progress
  • Assignee changed from Mark Zaslavskiy to Alexander Kaluzhny

#4 Updated by Mark Zaslavskiy over 5 years ago

  • Priority changed from Normal to Low

#5 Updated by Alexander Kaluzhny over 5 years ago

  • Status changed from Active / In progress to New

#6 Updated by Alexander Kaluzhny over 5 years ago

  • Status changed from New to Active / In progress

#7 Updated by Alexander Kaluzhny over 5 years ago

  • Sprint/Milestone changed from 0.83 to backlog

Repo checking is done, but found some strange behavior of repo links:
http://maxscale-jenkins.mariadb.com:8090/job/mdbci_integration_test/203/console

Concrete error: ================================================================================
INFO: > maxscale: Error executing action `install` on resource 'yum_package[net-tools]'
INFO: > maxscale: ================================================================================
INFO: > maxscale:
INFO: > maxscale: Mixlib::ShellOut::ShellCommandFailed
INFO: > maxscale: ------------------------------------
INFO: > maxscale: Expected process to exit with [0], but received '1'
INFO: > maxscale: ---- Begin output of /usr/bin/python /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/provider/package/yum-dump.py --options --installed-provides --yum-lock-timeout 30 ----
INFO: > maxscale: STDOUT: [option installonlypkgs] kernel kernel-bigmem installonlypkg(kernel-module) installonlypkg(vm) kernel-enterprise kernel-smp kernel-debug kernel-unsupported kernel-source kernel-devel kernel-PAE kernel-PAE-debug
INFO: > maxscale: STDERR: yum-dump Repository Error: failure: repodata/repomd.xml from maxscale: [Errno 256] No more mirrors to try.
INFO: > maxscale: http://maxscale-jenkins.mariadb.com/ci-repository/release-1.3.0-debug/mariadb-maxscale//centos/7/x86_64/repodata//repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
INFO: > maxscale: ---- End output of /usr/bin/python /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/provider/package/yum-dump.py --options --installed-provides --yum-lock-timeout 30 ----
INFO: > maxscale: Ran /usr/bin/python /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/provider/package/yum-dump.py --options --installed-provides --yum-lock-timeout 30 returned 1

Link from JSON file with repositories looks like http://maxscale-jenkins.mariadb.com/ci-repository/release-1.3.0-debug/mariadb-maxscale//centos/7/$basearch and should be automatically replaced with http://maxscale-jenkins.mariadb.com/ci-repository/release-1.3.0-debug/mariadb-maxscale//centos/7/x86_64/repodata//repomd.xml but it's not happening and result link looks like http://maxscale-jenkins.mariadb.com/ci-repository/release-1.3.0-debug/mariadb-maxscale//centos/7/x86_64/repodata//repodata/repomd.xml and this link is dead

#8 Updated by Alexander Kaluzhny over 5 years ago

  • Status changed from Active / In progress to New

#9 Updated by Mark Zaslavskiy over 5 years ago

  • Status changed from New to Won't fix

Also available in: Atom PDF