---
# System prepended metadata

title: 20220425_dusty-lakshmi-s390x-notes

---

# 20220425_dusty-lakshmi-s390x-notes


- [ ] get familiar with [CoreOS Assembler](https://coreos.github.io/coreos-assembler/)
    - [x] Do a cosa build of a qemu image (x86_64)
successfully generated fedora-coreos-35.20220427.dev.0-qemu.x86_64.qcow2
    - [ ] Run kola tests on qemu image (x86_64)

Lakshmi: in my case, I have access to a x86 guest brought on s390x machine. 
The x86 guest runs out of space as I run cosa kola. 
It will take some cycles to get the resources increased for it with the test lab team.
it does not proceed after the point
---PASS: ext.config.root-reprovision.filesystem-only (87.24s)

-- will re-execute the tests on x86 cloud instance on IBM cloud.

- [ ] run docs steps for creating/running x86_64 instance in IBM Cloud
    - These use the IBM Cloud CLI, which is important because the steps are reproducible
    - https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-ibmcloud/

Lakshmi: Able to follow the steps in the document.
problems:
1. the x86 qcow built on s390x failed to upload to ibm cloud
2. downloaded fedora x86 image from public site and able to launch vm instance.
3. unable to ssh, the steps to link Floating IP to vm instance looks not correct in the documentation

- [x] run cosa build for s390x (qemu)
- [x] run kola tests for s390x (qemu)

Lakshmi: able to build and run kola tests for s390x fedora image.
test logs are here - https://ibm.ent.box.com/file/950268101118

```
[rexuser@m13lp36 ~]$ cat cosa_kola_s390x | grep FAIL
    Process: 1700 ExecStart=/usr/local/bin/kola-runext-test.sh (code=exited, status=1/FAILURE)
   Main PID: 1700 (code=exited, status=1/FAILURE)
Apr 27 11:11:11 qemu0 systemd[1]: kola-runext.service: Main process exited, code=exited, status=1/FAILURE
--- FAIL: ext.config.clhm.ignition-warnings (64.84s)
--- FAIL: ostree.hotfix (61.17s)
    --- FAIL: ostree.hotfix/unlock (4.61s)
--- FAIL: rpmostree.install-uninstall (1031.31s)
    --- FAIL: rpmostree.install-uninstall/install (351.71s)
    --- FAIL: rpmostree.install-uninstall/uninstall (623.26s)
--- FAIL: multipath.day2 (84.79s)
--- FAIL: rpmostree.upgrade-rollback (76.11s)
    --- FAIL: rpmostree.upgrade-rollback/upgrade (49.44s)
    Process: 5977 ExecStart=/usr/local/bin/kola-runext-file-directory-permissions (code=exited, status=1/FAILURE)
   Main PID: 5977 (code=exited, status=1/FAILURE)
Apr 27 12:47:02 qemu0 systemd[1]: kola-runext-12.service: Main process exited, code=exited, status=1/FAILURE
--- FAIL: non-exclusive-test-bucket-0 (267.81s)
    --- FAIL: non-exclusive-test-bucket-0/ext.config.files.file-directory-permissions (5.21s)
FAIL, output in tmp/kola
```


- [ ] launch IBM Cloud s390x instance (RHEL) and try to run cosa build on it

- [ ] s390x IBMCloud
    - [ ] build s390x IBMCloud artifact (wherever you like)
    - [ ] try to upload to IBMCloud and start an instance with it

Lakshmi: as I follow the document instructions
- able to bring up the vm instance - the instance comes up running 
problems:
it still recognises the architecture to be amd64 rather than s390x

- assigning a Floating IP and linking to the vnic works but ssh to it does not
- trying to bring up the instance in the UI rather than cli to verify the instructions 

notes:
- enable metadata via ibm cloud cli