Install and enable zsh in Compute node
User louistw
can't access the virt node because the shell, /usr/local/bin/zsh
, for this user is missing in the built image.
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Eesaan Atluri added Backlog label
added Backlog label
- Bo-Chun Chen changed the description
changed the description
- Owner
@mhanby how did you install this zsh on Cheaha? We tried to install zsh via yum, but it doesn't provide
/usr/local/bin/zsh
. Also the version is different. - Eesaan Atluri changed the description
changed the description
- Ravi Tripathi added Sprint 22-19 label and removed Backlog label
added Sprint 22-19 label and removed Backlog label
- Ravi Tripathi assigned to @louistw
assigned to @louistw
- Ravi Tripathi changed milestone to %ood nightly builds
changed milestone to %ood nightly builds
- Bo-Chun Chen mentioned in merge request !16 (merged)
mentioned in merge request !16 (merged)
- Ravi Tripathi added Sprint 22-20 label and removed Sprint 22-19 label
added Sprint 22-20 label and removed Sprint 22-19 label
- Owner
Got this error in the pipeline:
configure: error: no controlling tty
Collapse replies - Owner
Found this: https://www.linuxfromscratch.org/blfs/view/7.5/postlfs/zsh.html
Using a script to build with "su -c script" may produce a funny configure error message: "no controlling tty". If this happens, add the switch --with-tcsetpgrp to configure.
While I am not sure if ansible uses
su -c script
to execute the command, I did see the error message, so adding this switch to configure at louistw/packer-openstack-hpc-image@a50ddc4d - Owner
You can find the result of the build with this fix at HERE, it went smoothly.
I am able to ssh to the knightly instance with this fix in place.
- Please register or sign in to reply
- Bo-Chun Chen mentioned in commit 0757ffbe
mentioned in commit 0757ffbe
- Bo-Chun Chen closed with merge request !16 (merged)
closed with merge request !16 (merged)
- Bo-Chun Chen marked this issue as related to #23
marked this issue as related to #23