or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing
xxxxxxxxxx
tags: Reproducer
Reproduce Upstream CI failure on my machine aka Lab deployment with libvirt reproducer
Table of Contents
Requirements
a. 8 core cpu, 32 GB memory, 60GB freespace
b. CentOS-8,
RHEL-8 is not supported for now by reproducer and requires some work due to podman <> docker conflict
Hardware Prepare
You can use the root or non-root user.
Non-root users should have sudo access.
By default RHEL-8 comes with runc.x86_64 which is required for podman. In order to make docker working we need to install and use containerd instead.
Software prepare for reproducer
Prepare ssh keys
Test access by running, using your username
Prepare images
Some images are ~10Gb and some are ~5GB. The smaller one may not have python or yum installed. You may need to add those packages using
I would recommend to read Modify Images Guide which is very useful if you need to customize image for some experiments
Reproducing job
Cleanup
Debuging
There are a lot of possible issues with reproducer. I am not going to describe them all. The engineer with good debugging skills will be able to find them. Going back to my issue, after running
In this case we need to check the logs of zuul-scheduler container
So, I see
So, In this particular case ssh-key is not added to https://review.opendev.org. Once I added public part of ssh key to https://review.opendev.org the job went through without any issues.