Unable to assign ip address

[Kimberly Westfall]

 

Using the “Creating FABnet IPv4 Network” notebook (as well as other notebooks) I am failing at:

node1_iface.ip_addr_add(addr=node1_addr, subnet=network1.get_subnet())

I get an “Authentication failed” error, but my key has worked previously and is not expired. I tried setting up a new key anyway, and ran configure and “configure & validate” with no success. Wondering if it’s an error with the mgmt interface instead of an authentication error.

Slice ID is 72822f32-9878-4aa9-9895-0e193d52a39c

Any ideas?

[Kimberly Westfall]

 

 

Reattaching to see if these are more visible.

Nodes are at BRIST and STAR

[Komal Thareja]

Hi Kim,

Both of your VMs are accessible via SSH. I can verify with Nova SSH key. I also verified that your SSH keys are pushed in to the VM.

Could you please share the output of the following?
Please run the following snippet in a notebook cell before the configure step.
If this does show the management IPs for the VMs, please try running the configure cells again and let us know if it works.


slice = fablib.get_slice(slice_name)

slice.show();

slice.list_nodes();

Thanks,
Komal

[Hussam Nasir]

Can you also please provide more details like

1. you fabric user id
2. slicename/slice details.

[Kimberly Westfall]

<caption>Slice</caption>

ID	72822f32-9878-4aa9-9895-0e193d52a39c
Name	MySlice
Lease Expiration (UTC)	2024-10-01 14:30:22 +0000
Lease Start (UTC)	2024-09-30 14:30:22 +0000
Project ID	990d8a8b-7e50-4d13-a3be-0f133ffa8653
State	StableOK

 

<caption>Nodes</caption>

ID	Name	Cores	RAM	Disk	Image	Image Type	Host	Site	Username	Management IP	State	Error	SSH Command	Public SSH Key File	Private SSH Key File
91997e55-dc1f-4db6-8140-43a258236927	Node1	2	8	10	default_rocky_8	qcow2	brist-w2.fabric-testbed.net	BRIST	rocky	137.222.230.26	Active		ssh -i /home/fabric/work/fabric_config/slice_key -F /home/fabric/work/fabric_config/ssh_config rocky@137.222.230.26	/home/fabric/work/fabric_config/slice_key.pub	/home/fabric/work/fabric_config/slice_key
c3ff04c2-355e-4447-98cc-73ea3ddd843b	Node2	2	8	10	default_rocky_8	qcow2	star-w3.fabric-testbed.net	STAR	rocky	2001:400:a100:3030:f816:3eff:fecb:cff3	Active		ssh -i /home/fabric/work/fabric_config/slice_key -F /home/fabric/work/fabric_config/ssh_config rocky@2001:400:a100:3030:f816:3eff:fecb:cff3	/home/fabric/work/fabric_config/slice_key.pub	/home/fabric/work/fabric_config/slice_key

 

 

<caption>FABlib Config</caption>

Credential Manager	cm.fabric-testbed.net
Orchestrator	orchestrator.fabric-testbed.net
Project ID	990d8a8b-7e50-4d13-a3be-0f133ffa8653
Token File	/home/fabric/.tokens.json
Bastion Host	bastion.fabric-testbed.net
Bastion Username	kw26_0000131232
Bastion Private Key File	/home/fabric/work/fabric_config/new-bastion-keypair.pub
Slice Private Key File	/home/fabric/work/fabric_config/slice_key
Slice Public Key File	/home/fabric/work/fabric_config/slice_key.pub
Log File	/tmp/fablib/fablib.log
Log Level	INFO
Sites to avoid
SSH Command Line	ssh -i {{ _self_.private_ssh_key_file }} -F /home/fabric/work/fabric_config/ssh_config {{ _self_.username }}@{{ _self_.management_ip }}
Version	1.7.3
Data directory	/tmp/fablib
Core API	uis.fabric-testbed.net
Bastion SSH Config File	/home/fabric/work/fabric_config/ssh_config

 

 

Userid: kw26_0000131232

Slicename: MySlice

[Komal Thareja]

Thank you Kim! Could you also please open a terminal on JH and try SSH to the VM using the command displayed above?

ssh -i /home/fabric/work/fabric_config/slice_key -F /home/fabric/work/fabric_config/ssh_config rocky@137.222.230.26

Thanks,
Komal

[Kimberly Westfall]

fabric@spring:jupyter-examples-main-48%$ ssh -i /home/fabric/work/fabric_config/slice_key -F /home/fabric/work/fabric_config/ssh_config rocky@137.222.230.26
Warning: Permanently added 'bastion.fabric-testbed.net' (ED25519) to the list of known hosts.
Load key "/home/fabric/work/fabric_config/new-bastion-keypair.pub": error in libcrypto
kw26_0000131232@bastion.fabric-testbed.net: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
kex_exchange_identification: Connection closed by remote host
Connection closed by UNKNOWN port 65535

[Kimberly Westfall]

I reconfigured my key again and can ssh now. Not sure why my original key stopped working, but must have not set it up correctly the second time. So sorry, thanks for looking into it.

[Kimberly Westfall]

Unless the key disappears from the portal once it expires. Anyway, thanks for your time and help. Closing this.

[Author]

Posts