ACS 4.2X - ISCSI / ISO uploading horror...

[Ecsi1337]

Hi all!

I'm just getting to know the system, but can someone explain to me why I can't upload a simple ISO file to this system?
I've tried it in Advanced / Basic mode, at home and in a test environment in an untagged network. The "Register ISO" button appears for hours after the first installation, then when uploading I get the error "Failed to upload ISO. - Error: Network Error". There are a lot of videos about the installation, but not much about how what is good for what and what and where how to use it. For example: There are 0 videos about ISCSI storage setup.

Since everything is in a network, the SSVM also has 2 IPs.
The State running, the Agent Up is in the state, so everything is green and everything responds to ping. The forums have been full of this error for years, without a specific solution. Many people have "browser" blocking errors, and others say it will work on HTTPS, but there is no information about this.

So what is this system that can't jump the ISO upload level? Why does it work so easily in other hypervisors Hyper-V, oVirt, Proxmox, Xcp-ng?

I would appreciate any help to get both the ISO upload and the ISCSI setup working in a simple 192.168.0.0/24 network without vlaning.

[prashanthr2]

@Ecsi1337

If you’re hosting the ISO on an internal web server and attempting to upload it from there, please ensure that the CIDR of the internal web server is allowed by configuring the global setting secstorage.allowed.internal.sites.

If the URL you’re using is external (on the internet), refer to the following link for troubleshooting steps related to template or ISO upload issues:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM%2C+templates%2C+Secondary+storage+troubleshooting

If you’re still unable to identify the cause, please reproduce the issue and share the following logs covering the time of occurrence:

/var/log/cloudstack/management-server.log from the CloudStack management servers
/var/log/cloud.log from the SSVM

[Ecsi1337]

I would upload it from my computer with drag and drop.
Others have complained similarly here:
#10130

I didn't get any questions about https or how to set up iscsi

management-server.log

[prashanthr2]

@Ecsi1337 for the upload from local.

It could be failing as a result of either of the below issues

1. Public IP of the SSVM not reachable from the desktop/machine from where you are trying to upload. CHeck and confirm if you can access SSVM public on port 443

2. If no issues with the port. It could be as a result of ssl cert on the SSVM. By default, the SSL cert is self-signed and is not accepted by the browsers.

Try to upload the ISO from local, once it fails open a new tab and visit https://<<public_ip_ssvm/upload, here accept the cert and continue. Once done, go back to cloudstack tab and try the upload again. It should work now

[Ecsi1337]

This really works, and thanks for the answer.
Why isn't this described anywhere? I spent a lot of time on this, but I couldn't find this answer anywhere. Also, I still don't know why the "Register ISO" button only appears "by itself" after hours, and I don't know how to properly add iscsi storage to the system

[kiranchavala]

@Ecsi1337

You could follow these steps for troubleshooting purpose

#7568 (comment)

[ddiconza]

I think you're having the following problem: the ISOs are uploaded to secondary storage (only supports NFS/CIFS/S3/SWIFT). I don't know where you defined ISCSI. The uploader is the VM. SSVM must be active and have both IP addresses accessible.
If you have an http://xxxx file with the uploaded ISOs, the SSVM's external IP address must be able to reach
the URL http://xxxx.
After uploading the ISO with the URL http://xxxx, try downloading directly and not directly from the CloudStack Manager.
Excuse my English.

[Ecsi1337]

@prashanthr2
There is an "Upload ISO from local" button. Is this just for decoration? The iscsi problem is not relevant here, I was just wondering how it works, and why do you have to wait hours for the "register iso" button to appear?

As I wrote, the SSVM is green, it has two IP addresses, and I can ping them, but nothing works yet.

[Ecsi1337]

I would also be interested in where I can enable "CPU Passthrough" for the VM?

[ddiconza]

CPU Passthrough for the VM or GPU ? ( https://www.youtube.com/watch?v=aYGgUpKth7I)Yes it is GPU but I never did it

[rajujith]

@Ecsi1337 'secstorage.proxy' in Global settings.

[Ecsi1337]

@rajujith @prashanthr2
Since I set it up, I've been getting this:

PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

[Ecsi1337]

I only use the system on an internal local network, I don't have a public address.

[prashanthr2]

@Ecsi1337 For the query below

>>Can I change this afterwards? Do I need to issue a command somewhere after making the change or does this have to be done before adding the host?

After making the changes, restart the cloudstack-agent on the hosts. Once done, for the changes to take affect on the existing VM, you will need to stop and start them from cloudstack. New VM's deployed after the changes should take them in.

[Ecsi1337]

@prashanthr2
No matter how I set it up, no matter how I restarted the management vm, cpvm and ssvm, it has no effect. Only this "PKIX path building failed..."

[weizhouapache]

@Ecsi1337
does the issue still exist ?