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

Aborted setup doesnt terminate microcloud join #520

Open
tomponline opened this issue Dec 2, 2024 · 0 comments · May be fixed by #525
Open

Aborted setup doesnt terminate microcloud join #520

tomponline opened this issue Dec 2, 2024 · 0 comments · May be fixed by #525
Labels
Bug Confirmed to be a bug Jira Allows the synchronization of a GitHub issue in Jira

Comments

@tomponline
Copy link
Member

root@v1:~# snap list
Name        Version                 Rev    Tracking       Publisher   Notes
core22      20241001                1663   latest/stable  canonical✓  base
core24      20240920                609    latest/stable  canonical✓  base
lxd         5.21.2-084c8c8          31214  5.21/stable    canonical✓  -
microcloud  2.1.0-3e8b183           1144   2/stable       canonical✓  -
microovn    24.03.2+snapa2c59c105b  667    24.03/stable   canonical✓  -
snapd       2.66.1                  23258  latest/stable  canonical✓  snapd
root@v1:~# microcloud init
Waiting for services to start ...
Do you want to set up more than one cluster member? (yes/no) [default=yes]: 
Select an address for MicroCloud's internal traffic:

 Using address "10.19.164.17" for MicroCloud

MicroCeph not found. Continue anyway? (yes/no) [default=yes]: 
Use the following command on systems that you want to join the cluster:

 microcloud join

When requested enter the passphrase:

 oftentimes rupture saxophone buzzard

Verify the fingerprint "106a729df5d6" is displayed on joining systems.
Waiting to detect systems ...

 Selected "v2" at "10.19.164.247"
 Selected "v1" at "10.19.164.17"

Gathering system information ...
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_vol1" on "v1" for local storage pool
 Using "/dev/disk/by-id/scsi-SQEMU_QEMU_HARDDISK_lxd_vol1" on "v2" for local storage pool

Some systems are ineligible for distributed networking, which requires either an interface with no IPs assigned or a bridge. Continue anyway? (yes/no) [default=yes]: no
Error: User aborted

on joining member microcloud join is hanging:

root@v2:~# microcloud join
Waiting for services to start ...
Select an address for MicroCloud's internal traffic:

 Using address "10.19.164.247" for MicroCloud

Verify the fingerprint "f133cfdb303c" is displayed on the other system.
Specify the passphrase for joining the system: oftentimes rupture saxophone buzzard
Searching for an eligible system ...

 Found system "v1" at "10.19.164.17" using fingerprint "106a729df5d6"

Select "v2" on "v1" to let it join the cluster

 Received confirmation from system "v1"

Do not exit out to keep the session alive.
Complete the remaining configuration on "v1" ...
@tomponline tomponline added the Bug Confirmed to be a bug label Dec 2, 2024
@mseralessandri mseralessandri added the Jira Allows the synchronization of a GitHub issue in Jira label Dec 2, 2024
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
2 participants