It would be useful to know if the system is pingable at the assigned
network IP
and ssh -vvv output would be useful to see if there's an ssh connection vs.
ssh not available on the port.
On Wed, Apr 19, 2017 at 10:10 AM, Newell Jensen <<email address hidden>
> wrote:
> Ryan,
>
> Intel is still in the process of upgrading the software on their PODM
> and they have deleted all the machines we were using but once I get
> access again I will include the boot log.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1683910
>
> Title:
> Can't SSH into deployed node that has an iSCSI disk.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1683910/+subscriptions
>
OK.
It would be useful to know if the system is pingable at the assigned
network IP
and ssh -vvv output would be useful to see if there's an ssh connection vs.
ssh not available on the port.
Some curtin debugging commands/tips here:
https:/ /gist.github. com/smoser/ 2610e9b78b8d7b5 4319675d9e3986a 1b
On Wed, Apr 19, 2017 at 10:10 AM, Newell Jensen <<email address hidden>
> wrote:
> Ryan, /bugs.launchpad .net/bugs/ 1683910 /bugs.launchpad .net/curtin/ +bug/1683910/ +subscriptions
>
> Intel is still in the process of upgrading the software on their PODM
> and they have deleted all the machines we were using but once I get
> access again I will include the boot log.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Can't SSH into deployed node that has an iSCSI disk.
>
> To manage notifications about this bug go to:
> https:/
>