bamahat: IDK if you have done any of the work already to replace stud in the portal, but I updated the portal-orchestration code to replace stud with haproxy. But I no longer have access to the repo to commit my changes. If you'd like the changes let me know.

I've got a triton compute node PI 20221215T000744Z for some reason when I rebooted into the newer version the VM hosted on that box stopped being accessible on the network. I determined there were too underlay vnics 0 and 1 and two different IP addresses at that. I do not think it was like that before the update.

There is only one underlay nictag however

I deleted one of the underlays from napi, removed the VM's fabric nic, rebooted the compute node, and it went back to only underlay0. Then I added a new NIC to the VM. But it refuses to work. I am at a loss

When I run dladm show-overlay I see the VM nic setup correctly, `vmadm get VM | json nics` looks correct, but you cannot ping the VM. I went in under single user mode in the guest and enabled networking (ubuntu 2204), the nic looks right, but I cannot ping anything on the fabric within the guest.

I can ping other hosts from the GZ on the underlay VLAN so it can't be an MTU/VLAN issue

okay I found the problem with the overlay in portolan. Now to figure out how to fix it

anyone have any idea how to reassociate an underlay nic with a compute node uuid in portolan?

Everything looks to match other working compute nodes in sdc-napi.

for future reference: portolan add-underlay --cn <UUID> --ip <cn_underlay_ip>

boom back in business

nice

odd that portolan's path doesn't include the correct node path though

I slapped a symlink in /opt/smartdc/portolan to /opt/smartdc/portolan/build/node

Otherwise, the "portolan" command died with /usr/bin/env no such node

Too bad theres no "portolan list-underlay"

or help lmao

barfield: No idea what you're talking about there. If portolan didn't have the right path to node then the service would be completely broken.

I think that smf calls the correct path

but bash login doesn't

well

let me rephrase that

It's not supposed to.

/opt/smartdc/portolan/node just doesn't exist

but I found it in /opt/smartdc/portolan/build

so cd /opt/smartdc/portolan; ln -s build/node

makes `portolan` and `portolanadm` work

Ah.

here is the PATH

/usr/local/sbin:/usr/local/bin:/opt/local/sbin:/opt/local/bin:/usr/sbin:/usr/bin:/sbin:/opt/smartdc/portolan/node/bin:/opt/smartdc/portolan/node_modules/.bin:/opt/smartdc/portolan/bin

Good thing I've spent some time playing with sdcnode recently lol

and here it is:

/usr/bin/ctrun -l child -o noorphan /opt/smartdc/portolan/build/node/bin/node --abort_on_uncaught_exception /opt/smartdc/portolan/server.js &

/opt/smartdc/portolan/smf/method/portolan is what starts the SMF

Created TRITON-2359

that was fast!

sdc-portolan#9

TritonDataCenter/sdc-portolan#9