jdoss reported a new issue against the project: `cloud-sig` that you are following:
``
When starting the F28 vagrant image it fails with the error below due to `/etc/sysconfig/network-scripts/ifcfg-enp0s3` being kept by the build process. Removing this file fixes the issue.
```
==> f28: Setting hostname...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
# Update sysconfig
sed -i 's/\(HOSTNAME=\).*/\1f28.example.com/' /etc/sysconfig/network
# Update DNS
sed -i 's/\(DHCP_HOSTNAME=\).*/\1"f28"/' /etc/sysconfig/network-scripts/ifcfg-*
# Set the hostname - use hostnamectl if available
echo 'f28.example.com' > /etc/hostname
if command -v hostnamectl; then
hostnamectl set-hostname --static 'f28.example.com'
hostnamectl set-hostname --transient 'f28.example.com'
else
hostname -F /etc/hostname
fi
# Prepend ourselves to /etc/hosts
grep -w 'f28.example.com' /etc/hosts || {
sed -i'' '1i 127.0.0.1\tf28.example.com\tf28' /etc/hosts
}
# Restart network
service network restart
Stdout from the command:
/usr/bin/hostnamectl
Restarting network (via systemctl): [FAILED]
Stderr from the command:
Job for network.service failed because the control process exited with error code.
See "systemctl status network.service" and "journalctl -xe" for details.
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/cloud-sig/issue/283
_______________________________________________
cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
