#NAbox 4.0.7 is available

1 messages · Page 1 of 1 (latest)

severe ferry
#
  • fix: qcow2 images wouldn't use eth0 by default
  • fix: enable guest access to Grafana would not work if Grafana organization name had been changed
  • fix: web site aborts upgrade package upload after 60s
  • fix: wrong permission in upgrade file would break NAbox during manual upgrades
  • new: migrate tool for NAbox 3 can be run with -debug for troubleshooting
  • Grafana 11.2
  • Base OS upgrade (Flatcar Container Linux 3975.2.1)
jade lion
#

Just installed, configured and started a upgrade of a system with 4 clusters and quite some history.
The network startup file was not created. Did that by hand.
Installed Harvest and started migrating. Still running. But a well documented smooth experience so far!

severe ferry
#

Thanks Martijn ! I'm worried that the network startup file wasn't created. Is that on VMware ? Did you setup networking in vCenter deployment or did you leave it blank ?
Harvest wasn't installed already ?

jade lion
severe ferry
#

So no /etc/systemd/network/10-nabox.network ?

jade lion
#

Migration finished. I had to re-enter the passwords for data collection to start after the migration.

jade lion
severe ferry
jade lion
#

Sure!

severe ferry
#

Thanks !

jade lion
#

It's there!

#

Just another note: the Grafana item on the About screen has a question mark and not the version number

#

Uploaded a screenshot

severe ferry
#

Yeah I see that. You changed the default password didn't you ?

jade lion
#

Yes, sir 😉 Standard practice

#

But after the migration

severe ferry
#

Ok there is some weird race condition with setting up grafana auth I'll try and track that in the logs

#

and I see the issue with network config I think

jade lion
#

Did I make a typo?

severe ferry
#

No I think it's a bug. just trying to understand why I didn't hit it !

#

How did you configure ip btw ? Originally. Static ip or dhcp in vcenter screen ?

jade lion
#

Static!

severe ferry
#

With the netmask in the IP address ?

severe ferry
#

I think I got it

jade lion
severe ferry
#

for the grafana thing, what you can do is regenerate an api token for the nabox user, in grafana I think it exists, and put it in /etc/nabox/secrets/grafana-secret then systemctl restart naboxd

glass glacier
#

If you wanna test on my Harvest to make sure it works, feel free. If you break it you fix it. 😄

severe ferry
#

You don't have to tell me twice 😄

#

It'll take me a couple hours to get on VPN then I'm unleashed

#

NAbox 4.0.7 is available

jade lion
#

Should I update?

severe ferry
#

To be on the safe side but you shouldn't have any problem

jade lion
#

Just upgraded, will do the Grafana part today

jade lion
severe ferry
#

Yep that’s the problem. You can create a new “nabox” service account and paste the key in the grafana-secret file

jade lion
#

I only have three files. One with a typo:
havrest-secret; jwt-secret and a folder called ssl

#

It is even stranger. I do not see any service account in the gui. But when I try to create the nabox service account, it states: Service account already exists

jade lion
#

And I cannot log into grafana anymore...

#

Any help would be appreciated

#

I also see that the container name is havrest

severe ferry
#

Available for a remote session ?

#

havrest is the REST frontend that is wrapped around Harvest so that's normal

#

In grafana, that's the url where you should be able to see service accounts and there should be one for nabox : /grafana/org/serviceaccounts

#

and in nabox you should have one token created nabox

severe ferry
#

I keep asking right ? 😄 ok you can send me screeshots of the service accounts page

jade lion
#

First problem is: cannot log into grafana anymore. ssh and admin works fine

severe ferry
#

what version of NAbox ?

#

sent you a DM btw

jade lion
#

4.0.7

severe ferry
#

ok cool, so your credentials are denied ?

#

You can reset password in nabox admin page, it should reset grafana password as well

jade lion
#

Yeah: invalid username or password. I did a reset, still no access to grafana.

#

Will try again

severe ferry
#

watch journalctl -fu naboxd while doing it

jade lion
#

Sep 17 145058 naboxd[1454]: time=2024-09-17T145058.928Z level=ERROR source=main.go:131 msg="unable to create Grafana token" error="{"extra":null,"message"
:"Invalid username or password","messageId":"password-auth.failed","statusCode":401,"traceID":""}\n"

#

That is the login error, will now try reset

#

Sep 17 14:51:57 vsa-gra-002 naboxd[3991]: logger=migrator t=2024-09-17T14:51:57.155594775Z level=info msg="Unlocking database"
Sep 17 14:51:57 vsa-gra-002 naboxd[3991]: logger=secrets t=2024-09-17T14:51:57.156037725Z level=info msg="Envelope encryption state" enabled=true currentprovider=secretKey.v1
Sep 17 14:51:57 vsa-gra-002 naboxd[3991]: Admin password changed successfully
Sep 17 14:51:57 vsa-gra-002 chpasswd[4027]: pam_unix(chpasswd:chauthtok): password changed for admin
Sep 17 14:51:57 vsa-gra-002 naboxd[1454]: time=2024-09-17T14:51:57.233Z level=INFO source=password.go:71 msg="password changed" output=""
Sep 17 14:51:57 vsa-gra-002 naboxd[1454]: 2024/09/17 14:51:57 "POST http://vsa-gra-002/api/2.0/system/password HTTP/1.1" from 192.0.0.3:35848 - 200 30B in 324.075501ms
Sep 17 14:51:58 vsa-gra-002 naboxd[1454]: time=2024-09-17T14:51:58.954Z level=ERROR source=main.go:131 msg="unable to create Grafana token" error="{"extra":null,"message"
:"Invalid username or password","messageId":"password-auth.failed","statusCode":401,"traceID":""}\n"
Sep 17 14:51:59 vsa-gra-002 naboxd[1454]: time=2024-09-17T14:51:59.772Z level=ERROR source=auth.go:74 msg="authentication failed" errors="{"errors":["JWTAuthMiddleware: no
Authorization header","BasicAuthMiddleware: unable to read credentials"]}"
Sep 17 14:51:59 vsa-gra-002 naboxd[1454]: 2024/09/17 14:51:59 "GET http://vsa-gra-002/api/2.0/health HTTP/1.1" from 192.0.0.3:35848 - 401 107B in 103.832 s
Sep 17 14:52:08 vsa-gra-002 naboxd[1454]: time=2024-09-17T14:52:08.972Z level=ERROR source=main.go:131 msg="unable to create Grafana token" error="{"extra":null,"message"
:"Invalid username or password","messageId":"password-auth.failed","statusCode":401,"traceID":""}\n"

severe ferry
#

dc exec grafana grafana cli admin reset-admin-password <new password> ?

jade lion
#

yep, that did the trick. Can login again

#

Will look for the token now

severe ferry
#

weird, 4.0.7 should do exactly that

#

well, actually Admin password changed successfully comes from grafana

#

what was the output of the successful password change ?

jade lion
#

Paste it to the url you sent me.

#

Also a screenshot of the service accounts screen (nu users visible)

jade lion
#

@severe ferry Thanks for the amazing support

lusty igloo
#

trying to get this going on Azure and it fails to boot
after ~5minutes it just goes into a reboot cycle without actually ever starting

#

went through the same steps/process that I did to get 3.3 working. Converted the disk, uploaded, created new vm using the flatcar image, swapped the OS disk, started the system

severe ferry
#

You're probably missing the data disk

#

use the vhdx image, make a new vm and attach a data disk, just had a report today that it works 😄

lusty igloo
#

I created the second disk the same way and attached it.
This was with that attached, doing it without being attached yields the same problem.
Did they deploy in Azure? Should I just add a blank data disk instead of the one created by the ova?

severe ferry
#

No that was actual Hyper-V. Here is the thing, it seems that Azure image format provided by Flatcar is VHD, not VHDX.
The problem is the VHD is much bigger and I don't have space to uncompress it and pack it. That's why there is no VHD image

lusty igloo
#

I use qemu to convert the disk and then the powershell module "Add-AzVhd" to upload it

#

the unpacked image for disk1 is 8gb

#

qemu-img convert -p -f vmdk -O vpc -o subformat=fixed NAbox-disk1.vmdk NAbox-disk1.vhd
Add-AzVhd -LocalFilePath NAbox-disk1.vhd -ResourceGroupName rg-storage -Location eastus2 -DiskName NAbox_4.0.7_disk01 -DiskSKU Standard_LRS -DiskOsType Linux -DiskHyperVGeneration V1

lusty igloo
#

hrm. getting a little farther.
Booted the disk on my hyper-v machine, shut it down after it was successfully at the login prompt.
Used hyper-v to convert to vhd, uploaded and it passed the point it was at last time.
Now it's stuck at
hv_netvsc 6045bdb5-ff8f-6045-bdb5-ff8f6045bdb5 eth0: Data path switched from VF: enP21176s1

going to keep poking at it, see what can be done

#

that seems to have gotten it. after it times out and does an emergency shutdown/restart it boots and everything seems to work.
i'll finish the documents and pass them over to you for revision/etc

severe ferry
#

Don't use the VMDK as a base for Hyper-V, though, use the .zip

lusty igloo
#

aye, it is what i was using for the second round

severe ferry
#

I guess I'll need to make some space on my machine and use the actual azure image. Not sure why they don't provide it as vhdx

lusty igloo
#

they charge you by gb used, so the bigger the better 😮

lusty igloo
#

Is there any way to add another user or group or anything to nabox for the gui?

severe ferry
#

Not tested, but if you create a system user it should work to authenticate on the web UI as well. I'm considering extending the LDAP configuration to GUI as well, OAuth could also be an option.

lusty igloo
#

where are the ssl allowed ciphers/etc in the new version?
Accepted insecure ciphers: ECDHE-RSA-AES128-SHA256

also, our security team is reporting CSP misconfiguration failures
Port: TCP/443 (80)
Content-Security-Policy header mis-configured Affects:/
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Length: 520
Content-Type: text/html charset=utf-8
Date: Sun, 29 Sep 2024 11:14:39 GMT
Strict-Transport-Security: max-age=315360000 includeSubDomains preload
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Xss-Protection: 1 mode=block
Connection: close

Resolution: Implement or reconfigure the Content Security Policy with source directives.

severe ferry
#

You have /usr/share/nabox/traefik/dynamic/ssl.yaml and /usr/share/nabox/traefik/dynamic/hsts.yaml

#

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 is indeed accepted

lusty igloo
#

yea, the ssl.yaml file contains that entry, but it's read only filesystem

severe ferry
lusty igloo
#

pushing now. thanks
is this just the ssl changes?

severe ferry
#

It's both

lusty igloo
#

thanks.
verified the ssl one is fixed, waiting for sec team to rerun the rest of the scans to confirm the other.

severe ferry
#

Excellent !

lusty igloo
#

another question.
What is this interface and is it in use or can the ip range be changed?

3: br-27627dc19fd4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:95:02🆎49 brd ff:ff:ff:ff:ff:ff
inet 172.19.0.1/16 brd 172.19.255.255 scope global br-27627dc19fd4
valid_lft forever preferred_lft forever

severe ferry
#

mmm... That's not supposed to be here.
do you have another one with inet 192.0.0.1/24 ?

#

docker network ls ?

lusty igloo
#

docker network ls
NETWORK ID NAME DRIVER SCOPE
27627dc19fd4 build_default bridge local
e9468e9e41a5 host host local
af04ff016e87 nabox_default bridge local
6121605be548 none null local

#

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:3a:0d:ff:47 brd ff:ff:ff:ff:ff:ff
inet 172.25.1.38/24 brd 172.25.1.255 scope global eth0
valid_lft forever preferred_lft forever
3: br-27627dc19fd4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:95:02🆎49 brd ff:ff:ff:ff:ff:ff
inet 172.19.0.1/16 brd 172.19.255.255 scope global br-27627dc19fd4
valid_lft forever preferred_lft forever
4: br-af04ff016e87: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:34:3c:76:97 brd ff:ff:ff:ff:ff:ff
inet 192.0.0.1/24 brd 192.0.0.255 scope global br-af04ff016e87
valid_lft forever preferred_lft forever
inet6 fe80::42:34ff:fe3c:7697/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever

severe ferry
#

ok you can remove it

#

try docker network prune

#

You might need docker builder prune before

lusty igloo
#

ran both, that interface is showing gone. going to see if that fixed my issue.

#

aye, that seems to have done it.
no idea why it was there or where it came from

#

but thank you

#

is there any way to adjust the timeout on the gui

severe ferry
#

Some versions were distributed with leftovers from the build process, that's were it came from

#

you want it longer or shorter ?

#

currently it should be 20 minutes

lusty igloo
#

would be preferred if it was an option to set it to whatever you want, or disable it
not a huge thing

severe ferry
#

And we're talking about NAbox UI timeout or does that cover grafana as well ?

lusty igloo
#

nabox is what i was referring to

weary forge
#

Hi @severe ferry I just created a new 4.0.7 instance and when I want to open the dashboard I have to many redirect. The URL looks like https://<fqdn>/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/grafana/dashboards

this is from the native URL and also from the links in the admin UI

severe ferry
#

Mmmm, it does that if you go on « /grafana » or « /grafana/ » ?

weary forge
#

Over the UI it is /grafana/dashboards

severe ferry
#

Do you still have the issue ?

weary forge
severe ferry
weary forge
#

interesting - <a href="<fqdn>/grafana/grafana/dashboards">Moved Permanently</a>

severe ferry
#

Can you check GF_SERVER_ROOT_URL environment in Grafana container ?

weary forge
#

can you provide me a short how to? 🙈

severe ferry
#

dc exec grafana env|grep ROOT_URL

#

Should work

weary forge
#

GF_SERVER_ROOT_URL=https://%(domain)s/grafana/

#

that looks fine

#

and URL looks like

severe ferry
#

Mmm, did you actually try to delete web site data ?

weary forge
#

This was from the private mode but good point, I will delete the data and also use another browser

weary forge
#

same issue after deleting the web site data and with firefox

#

the login to the admin UI works it is only the grafana part

lusty igloo
#

There doesn't appear to be any way to change the Datacenter/logical group after a system is added to NAbox.

lusty igloo
#

Hey Yann, sorry to replay this, but the misconfigured CSP security alert came back on this weeks security scan, so it apparently has not been fixed

#

Content-Security-Policy header mis-configured Affects:/
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Length: 520
Content-Security-Policy: self
Content-Type: text/html charset=utf-8
Date: Sat, 05 Oct 2024 13:07:47 GMT
Strict-Transport-Security: max-age=315360000 includeSubDomains preload
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Xss-Protection: 1 mode=block
Connection: close
Resolution: Implement or reconfigure the Content Security Policy with source directives.

severe ferry
#

I might have forgotten the quotes around self.....

lusty igloo
#

guess there isn't an easy way to edit that

severe ferry
#

Your guess is right 🙂 it's on a read only part of the FS

lusty igloo
#

thanks, updated and we'll see what the security scan shows next time it runs.
anything that can be done about the ability to edit the datacenter name after the ontap systems are created?
or do you just have to delete them and create new ones and lose existing data

severe ferry
#

Whenever I looked into renaming metrics I think it ends up with reimporting the data somehow.

lusty igloo
#

GRR, still there
Evidence for reopened
Port: TCP/443/80
Content-Security-Policy header mis-configured Affects:/
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Length: 520
Content-Security-Policy: self
Content-Type: text/html charset=utf-8
Date: Sat, 05 Oct 2024 13:07:47 GMT
Strict-Transport-Security: max-age=315360000 includeSubDomains preload
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Xss-Protection: 1 mode=block
Connection: close

lusty igloo
#

@severe ferry Sorry to keep bugging you about this, but I can't make changes as it's RO

severe ferry
#

Mmm, it should be self with single quotes.

severe ferry
#

Ok I have no idea about CSP really. Maybe the expeceted syntax is something like default-src 'self';

lusty igloo
#

honestly don't know myself, i'll have to look into it to see what the error is actually being reported

lusty igloo
#

@severe ferry sent you a DM about the CSP stuff, not sure you get them or not