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

burn: ubuntu/rasbian: verify if temp command works after burning #40

Closed
laszewsk opened this issue Mar 10, 2021 · 6 comments
Closed

burn: ubuntu/rasbian: verify if temp command works after burning #40

laszewsk opened this issue Mar 10, 2021 · 6 comments
Assignees
Labels
1 priority one (highest) bug Something isn't working

Comments

@laszewsk
Copy link
Member

laszewsk commented Mar 10, 2021

I have merged the ubuntu branch into main. This requires a quality control check of burning an (at minimum) 3 node cluster. YOu can follow the appropriate tutorial. If such a tutorial does not exist on piplanet.org in tutorials, please create. If you see issues, report and or correct

[ Y] Richard MacOS
[Y ] Anthiny Linux
[ Y] Rama Pi
[ ] DK Pi

related to #28 and #30

@aporlowski
Copy link
Collaborator

aporlowski commented Mar 11, 2021

burn gui works for Linux. I had to push a few fixes just now

cluster from the commandline also works
cms burn cluster --hostname=red,red00[1-2] --ssid=NETGEAR19-5G -y --device=/dev/sdb

@laszewsk laszewsk changed the title Verification of burn in main after branch merge Verify DK issue with temp: Verification of burn in main after branch merge Apr 15, 2021
@laszewsk
Copy link
Member Author

laszewsk commented Apr 2, 2022

likely other modifications have been done. DK reports tutorials do not work, JP reports tutorial work

@laszewsk laszewsk added bug Something isn't working High Priority labels Apr 2, 2022
@laszewsk
Copy link
Member Author

laszewsk commented Apr 2, 2022

gregor was able to after he fixed the config file in .ssh to run temp on dks machine. THis it seems a documentation issue on how to create the right config file. DK does not post the errors properly just says its the same error as before, but which, he had different once

@laszewsk
Copy link
Member Author

laszewsk commented Apr 2, 2022

also dks issue is not yet related to ubuntu, but to rasbianos

@laszewsk laszewsk changed the title Verify DK issue with temp: Verification of burn in main after branch merge ubuntu/rasbian: Verify DK issue with temp: Verification of burn in main after branch merge Apr 2, 2022
@laszewsk laszewsk changed the title ubuntu/rasbian: Verify DK issue with temp: Verification of burn in main after branch merge burn: ubuntu/rasbian: Verify DK issue with temp: Verification of burn in main after branch merge May 2, 2022
@laszewsk laszewsk added the burn label May 2, 2022
@jpfleischer jpfleischer transferred this issue from cloudmesh/cloudmesh-pi-cluster May 2, 2022
@jpfleischer jpfleischer added 1 priority one (highest) and removed High Priority labels May 2, 2022
@laszewsk laszewsk assigned jpfleischer and unassigned dkkolli May 8, 2022
@laszewsk
Copy link
Member Author

laszewsk commented May 8, 2022

reassigned to JP.
just follow tutorial and if works, let us know so we can close this

@laszewsk laszewsk changed the title burn: ubuntu/rasbian: Verify DK issue with temp: Verification of burn in main after branch merge burn: ubuntu/rasbian: verify if temp command works after burning May 8, 2022
@jpfleischer
Copy link
Member

i am able to replicate this issue.

Sledgehammer@Sledgehammer MINGW64 ~
$ cms pi temp red,red0[1-3]
ERROR: not enough values to unpack (expected 2, got 0)
ERROR: not enough values to unpack (expected 2, got 0)
ERROR: not enough values to unpack (expected 2, got 0)
ERROR: not enough values to unpack (expected 2, got 0)
+--------+--------+-------+----------------------------+
| host   |    cpu |   gpu | date                       |
|--------+--------+-------+----------------------------|
| red    | 49.173 |  49.1 | 2022-05-11 13:15:47.525902 |
| red01  |  0     |   0   | 2022-05-11 13:15:49.123703 |
| red02  | 46.251 |  46.2 | 2022-05-11 13:15:48.622586 |
| red03  |  0     |   0   | 2022-05-11 13:15:50.259289 |
+--------+--------+-------+----------------------------+
# Timer: 3.9271s Load: 0.5881s pi temp red,red0[1-3]
(ENV3)
Sledgehammer@Sledgehammer MINGW64 ~
$ cat ~/.ssh/config



























##### CLOUDMESH PROXY CONFIG #####

Host red
     HostName red.local
     User pi
     StrictHostKeyChecking no

Host red01
     HostName red01.local
     User pi
     PreferredAuthentications publickey
     StrictHostKeyChecking no

Host red02
     HostName red02.local
     User pi
     PreferredAuthentications publickey
     StrictHostKeyChecking no

Host red03
     HostName red03.local
     User pi
     PreferredAuthentications publickey
     StrictHostKeyChecking no

Host red04
     HostName red04.local
     User pi
     PreferredAuthentications publickey
     StrictHostKeyChecking no

##### CLOUDMESH PROXY CONFIG #####


##### CLOUDMESH PROXY CONFIG red #####

Host red
     HostName red
     User pi
     PreferredAuthentications publickey
     StrictHostKeyChecking no

Host red01
     HostName red01
     User pi
     PreferredAuthentications publickey
     StrictHostKeyChecking no
     ProxyJump red

Host red02
     HostName red02
     User pi
     PreferredAuthentications publickey
     StrictHostKeyChecking no
     ProxyJump red

Host red03
     HostName red03
     User pi
     PreferredAuthentications publickey
     StrictHostKeyChecking no
     ProxyJump red

##### CLOUDMESH PROXY CONFIG red #####
(ENV3)
Sledgehammer@Sledgehammer MINGW64 ~

the solution is to manually delete the ~/.ssh/config file and start fresh.

after doing so, running cms host config --local=no --proxy=red red0[1-3] worked and temp worked fully for me.

$ cms pi temp red,red0[1-3]
+--------+--------+-------+----------------------------+
| host   |    cpu |   gpu | date                       |
|--------+--------+-------+----------------------------|
| red    | 50.147 |  49.1 | 2022-05-11 13:16:54.553520 |
| red01  | 46.251 |  46.2 | 2022-05-11 13:16:55.372313 |
| red02  | 47.225 |  47.2 | 2022-05-11 13:16:54.623518 |
| red03  | 45.277 |  45.2 | 2022-05-11 13:16:55.572259 |
+--------+--------+-------+----------------------------+
# Timer: 4.6478s Load: 0.5820s pi temp red,red0[1-3]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 priority one (highest) bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants