MilanHofmann opened a new issue, #7430:
URL: https://github.com/apache/cloudstack/issues/7430
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Virtual Router VM / service offering / shared storage
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.18
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Advanced Zone with NFS primary Storage.
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Ubuntu Focal Fossa
##### SUMMARY
<!-- Explain the problem/feature briefly -->
When overprovisioning factors are > 1, the virtual router vm for a new zone
is not able to boot and ends up in a kernel panic while trying to mount the
root volume.
By default a local storage service offering is picked for the router.
If an id of a service offering that uses shared storage is specified in the
global settings under router.service.offering it is ignored.
Somehow the Volumes attached to the working system and router vms (when
overprovisioning == 1) are not accessible via the UI and lead to 404.
Taking a look at the db entry they look like:
id: 26
account_id: 1
domain_id: 1
pool_id: 4
last_pool_id: NULL
instance_id: 21
device_id: 0
name: ROOT-21
uuid: 29537b97-e6d1-484b-9e06-92cd905ead8e
size: 5242880000
folder: NULL
path: 29537b97-e6d1-484b-9e06-92cd905ead8e
pod_id: NULL
data_center_id: 4
iscsi_name: NULL
host_ip: NULL
volume_type: ROOT
pool_type: NULL
disk_offering_id: 12
template_id: 3
first_snapshot_backup_uuid: NULL
recreatable: 1
created: 2023-04-10 11:51:38
attached: NULL
updated: 2023-04-10 11:51:40
removed: NULL
state: Ready
chain_info: NULL
update_count: 2
disk_type: NULL
vm_snapshot_chain_size: NULL
iso_id: NULL
display_volume: 1
format: QCOW2
min_iops: NULL
max_iops: NULL
hv_ss_reserve: NULL
provisioning_type: thin
external_uuid: NULL
passphrase_id: NULL
encrypt_format: NULL
The disk offering for the volume is type "shared".
In addition there is a second primary storage that was setup by accident,
always comes up again (after disabling), but has no visible resources attached
to it.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
Set overprovisioning to > 1 and create a new VPC.
<!-- Paste example playbooks or commands between quotes below -->
~~~
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
The virtual router vm should use the shared storage offering and boot.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
It ends up ina kernel panic mounting the root volume.
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
