xdk

Results 15 comments of xdk

``` The full traceback is: File "/tmp/ansible_ansible.builtin.pip_payload_gd_n4f6i/ansible_ansible.builtin.pip_payload.zip/ansible/module_utils/basic.py", line 1443, in get_bin_path bin_path = get_bin_path(arg=arg, opt_dirs=opt_dirs) File "/tmp/ansible_ansible.builtin.pip_payload_gd_n4f6i/ansible_ansible.builtin.pip_payload.zip/ansible/module_utils/common/process.py", line 44, in get_bin_path raise ValueError('Failed to find required executable "%s" in paths:...

> Yes, this is due to the fact you can't go from disabled to permissive without a reboot. The software only supports permissive and enforced is being planned. We will...

> Unfortunately no ; since you mentioned it might have something to do with running the playbook multiple times, I am underway fully redeploying the controller and start fresh. So...

A dump of found 'issues' `000000 04:59:47 [root@cpu site]# luna osimage kernel compute Traceback (most recent call last): File "/bin/luna", line 7, in CLI = Cli().main() File "/trinity/local/python/lib/python3.10/site-packages/luna/cli.py", line 109,...

> "osimage pack for compute already queued" normally means that another packing for that image was already in progress. It prevents it from being packed twice at the same time....

a hint - as I encountered the same issue today. Verify your subscription within the image. Also, within the image, run a `watch -n 0.1 "cat /etc/yum.repos.d/redhat.repo"` (Using Red Hat...

w00000t.... i think i may have solved it... ![image](https://github.com/clustervision/trinityX/assets/24566213/769d6a44-f2d5-4238-afac-c16f2c1cb938) What i did was posted here: https://www.linuxquestions.org/questions/linux-server-73/centos-7-does-not-boot-4175619015/ Like so... ``` cp /sbin/init /trinity/images/compute/sbin/init cp /lib/systemd/systemd /trinity/images/compute/lib/systemd/systemd luna osimage pack compute luna...

> There were two problems that you hit. There was indeed a bug in the cli where a returned call caused the python trace. That has been solved and will...

@stonezdj fun fact, I'm not upgrading. Both are clean installs :-) They simply show a difference in behavior. deployment structure **/somepath/harbor/v2.12.2/data**

> [@xdkreij](https://github.com/xdkreij) Do you mean that you observed the permission issue on a fresh installation of version v2.13.3? That's correct, both are (almost identical) clean install tests. One proceeds (2.12.2),...