Project

General

Profile

Actions

Bug #19995

closed

mira039 ansible error

Added by Kefu Chai almost 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Urgent
Category:
Test Node
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

while scanning a plain scalar in "/tmp/teuth_ansible_failures_qjgTAc", line 1, column 476 found unexpected ':' in "/tmp/teuth_ansible_failures_qjgTAc", line 1, column 483 Please check http://pyyaml.org/wiki/YAMLColonInFlowContext for details.

http://pulpito.ceph.com/kchai-2017-05-19_07:36:14-rados-wip-mgr-stats-kefu-2---basic-mira/


Related issues 1 (0 open1 closed)

Copied from sepia - Bug #18974: smithi130 ansible errorResolvedDavid Galloway02/17/2017

Actions
Actions #1

Updated by Kefu Chai almost 7 years ago

  • Copied from Bug #18974: smithi130 ansible error added
Actions #2

Updated by David Galloway almost 7 years ago

  • Status changed from New to Resolved

Yep, I noticed that in a few previous jobs the machine ran. What happened was someone reimaged the host with RHEL and didn't change it back to CentOS before unlocking it. The true error was:

fatal: [mira039.front.sepia.ceph.com]: FAILED! => {"changed": false, "failed": true, "msg": "https://cdn.redhat.com/content/htb/rhel/server/7/x86_64/os/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden\nTrying other mirror.\nTo address this issue please refer to the below knowledge base article\n\nhttps://access.redhat.com/solutions/69319\n\nIf above article doesn't help to resolve this issue please open a ticket with Red Hat Support.\n\n\n\n One of the configured repositories failed (Red Hat Enterprise Linux 7 Server HTB (RPMs)),\n and yum doesn't have enough cached data to continue. At this point the only\n safe thing yum can do is fail. There are a few ways to work \"fix\" this:\n\n     1. Contact the upstream for the repository and get them to fix the problem.\n\n     2. Reconfigure the baseurl/etc. for the repository, to point to a working\n        upstream. This is most often useful if you are using a newer\n        distribution release than is supported by the repository (and the\n        packages for the previous distribution release still work).\n\n     3. Disable the repository, so yum won't use it by default. Yum will then\n        just ignore the repository until you permanently enable it again or use\n        --enablerepo for temporary usage:\n\n            yum-config-manager --disable rhel-7-server-htb-rpms\n\n     4. Configure the failing repository to be skipped, if it is unavailable.\n        Note that yum will try to contact the repo. when it runs most commands,\n        so will have to try and fail each time (and thus. yum will be be much\n        slower). If it is a very temporary problem though, this is often a nice\n        compromise:\n\n            yum-config-manager --save --setopt=rhel-7-server-htb-rpms.skip_if_unavailable=true\n\nfailure: repodata/repomd.xml from rhel-7-server-htb-rpms: [Errno 256] No more mirrors to try.\nhttps://cdn.redhat.com/c
2017-05-19T07:37:28.474 INFO:teuthology.task.ansible.out:ontent/htb/rhel/server/7/x86_64/os/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden\n", "rc": 1, "results": []}

I reimaged the machine with Xenial and released it.

Actions

Also available in: Atom PDF