Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

microcloud init fails on CephFS when using IPv6 #380

Open
roosterfish opened this issue Aug 21, 2024 · 1 comment
Open

microcloud init fails on CephFS when using IPv6 #380

roosterfish opened this issue Aug 21, 2024 · 1 comment
Assignees
Labels
Bug Confirmed to be a bug Jira Allows the synchronization of a GitHub issue in Jira

Comments

@roosterfish
Copy link
Contributor

MicroCloud version: latest/edge
LXD version: latest/edge
MicroCeph version: latest/stable

When selecting an IPv6 addresses for MicroCloud, it looks to be failing during CephFS setup:

Error: Failed to mount "fd42:4c88:a791:d989:216:3eff:fe97:243c:6789,fd42:4c88:a791:d989:216:3eff:fe6d:c28e:6789:/" on "/tmp/lxd_cephfs_3143952555/mount" using "ceph": invalid argument

The complete questionnaire:

root@m1:~# microcloud init
Waiting for LXD to start...
Select an address for MicroCloud's internal traffic:

 Using address "fd42:4c88:a791:d989:216:3eff:fe97:243c" for MicroCloud

Limit search for other MicroCloud servers to fd42:4c88:a791:d989:216:3eff:fe97:243c/64? (yes/no) [default=yes]: 
Scanning for eligible servers ...

 Selected "m3" at "fd42:4c88:a791:d989:216:3eff:fe6d:c28e"
 Selected "m2" at "fd42:4c88:a791:d989:216:3eff:fea3:e648"
 Selected "m1" at "fd42:4c88:a791:d989:216:3eff:fe97:243c"

Would you like to set up local storage? (yes/no) [default=yes]: 
Select exactly one disk from each cluster member:

Select which disks to wipe:

 Using "/dev/disk/by-id/scsi-SQEMU_QEMU_HARDDISK_lxd_volm1--local" on "m1" for local storage pool
 Using "/dev/disk/by-id/scsi-SQEMU_QEMU_HARDDISK_lxd_volm2--local" on "m2" for local storage pool
 Using "/dev/disk/by-id/scsi-SQEMU_QEMU_HARDDISK_lxd_volm3--local" on "m3" for local storage pool

Would you like to set up distributed storage? (yes/no) [default=yes]: 
Select from the available unpartitioned disks:

Select which disks to wipe:

Do you want to encrypt the selected disks? (yes/no) [default=no]: 
 Using 1 disk(s) on "m3" for remote storage pool
 Using 1 disk(s) on "m2" for remote storage pool
 Using 1 disk(s) on "m1" for remote storage pool

Would you like to set up CephFS remote storage? (yes/no) [default=yes]: 
What subnet (either IPv4 or IPv6 CIDR notation) would you like your Ceph internal traffic on? [default: fd42:4c88:a791:d989::/64] 
Configure distributed networking? (yes/no) [default=yes]: 
Select an available interface per system to provide external connectivity for distributed network(s):

 Using "enp6s0" on "m1" for OVN uplink
 Using "enp6s0" on "m3" for OVN uplink
 Using "enp6s0" on "m2" for OVN uplink

Specify the IPv4 gateway (CIDR) on the uplink network (empty to skip IPv4): 10.23.252.1/24
Specify the first IPv4 address in the range to use on the uplink network: 10.23.252.100 
Specify the last IPv4 address in the range to use on the uplink network: 10.23.252.200 
Specify the IPv6 gateway (CIDR) on the uplink network (empty to skip IPv6): 
Specify the DNS addresses (comma-separated IPv4 / IPv6 addresses) for the distributed network (default: 10.23.252.1): 
Initializing a new cluster
 Local MicroCloud is ready
 Local LXD is ready
 Local MicroOVN is ready
 Local MicroCeph is ready
Awaiting cluster formation ...
 Peer "m3" has joined the cluster
 Peer "m2" has joined the cluster
Configuring cluster-wide devices ...
Error: Failed to mount "fd42:4c88:a791:d989:216:3eff:fe97:243c:6789,fd42:4c88:a791:d989:216:3eff:fe6d:c28e:6789:/" on "/tmp/lxd_cephfs_3143952555/mount" using "ceph": invalid argument
@roosterfish roosterfish added Bug Confirmed to be a bug Jira Allows the synchronization of a GitHub issue in Jira labels Aug 21, 2024
@roosterfish
Copy link
Contributor Author

Not sure about the format but maybe we are missing the brackets [ipv6] around the address?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Confirmed to be a bug Jira Allows the synchronization of a GitHub issue in Jira
Projects
None yet
Development

No branches or pull requests

2 participants