Latest RDO Packstack wants "network" serivcei for external networking, but is not available in CentOS Stream 9
3:56 p.m.
In the current packstack instructions for RDO here:
https://www.rdoproject.org/deploy/packstack/ under the Network section it states the
following:
"If you plan on having external network access to the server and instances, this is a
good moment to properly configure your network settings. A static IP address to your
network card, and disabling NetworkManager are good ideas."
But, then it shows not only disabling NetworkManager, but also enabling the
"network" service:
sudo systemctl disable firewalld;
sudo systemctl stop firewalld;
sudo systemctl disable NetworkManager;
sudo systemctl stop NetworkManager;
sudo systemctl enable network;
sudo systemctl start network
The problem is that CentOS Stream 9 no longer has or supports the "network"
service, as it has been deprecated.
Are there alternate instructions?
Or, can I configure as usual with NetworkManager and just diable it once the
configurations are working?
6:41 p.m.
New subject: Latest RDO Packstack wants "network" serivcei for external networking, but is not available in CentOS Stream 9
Hey,
The network service is provided by the `openstack-network-scripts` RPM:
https://buildlogs.centos.org/centos/9-stream/cloud/x86_64/openstack-bobca...
It provides the traditional network-scripts that were shipped with prior
version of CentOS:
❯ rpm2cpio openstack-network-scripts-10.11.1-4.el9s.x86_64.rpm| cpio -idmv
./etc/rc.d/init.d/network
./etc/sysconfig/network-scripts
./etc/sysconfig/network-scripts/ifcfg-lo
./etc/sysconfig/network-scripts/ifdown
./etc/sysconfig/network-scripts/ifdown-eth
./etc/sysconfig/network-scripts/ifdown-ipv6
./etc/sysconfig/network-scripts/ifdown-ovs
./etc/sysconfig/network-scripts/ifdown-post
./etc/sysconfig/network-scripts/ifdown-routes
./etc/sysconfig/network-scripts/ifdown-tunnel
./etc/sysconfig/network-scripts/ifup
./etc/sysconfig/network-scripts/ifup-aliases
./etc/sysconfig/network-scripts/ifup-eth
./etc/sysconfig/network-scripts/ifup-ipv6
./etc/sysconfig/network-scripts/ifup-ovs
./etc/sysconfig/network-scripts/ifup-post
./etc/sysconfig/network-scripts/ifup-routes
./etc/sysconfig/network-scripts/ifup-tunnel
./etc/sysconfig/network-scripts/init.ipv6-global
./etc/sysconfig/network-scripts/network-functions
./etc/sysconfig/network-scripts/network-functions-ipv6
./usr/lib/.build-id
./usr/lib/.build-id/c6
./usr/lib/.build-id/c6/0310d942a9358873e333d2e576e1ba0b1b68e1
./usr/sbin/usernetctl
329 blocks
This was mainly for compatibility reasons. Projects like os-net-config are
implementing support for nmstate - which should already be available and
functional. It probably needs to stabilize before that documentation can be
updated to remove the Network service reference. Although, it should be
updated now to include a step for installing this package.
If you just install that openstack-network-scripts RPM, then you should be
able to continue following the documented steps.
All the best,
Regards,
Brendan Shephard
Senior Software Engineer
Red Hat APAC <https://www.redhat.com>
@RedHat <https://twitter.com/redhat> Red Hat
<https://www.linkedin.com/company/red-hat> Red Hat
<https://www.facebook.com/RedHatInc>
<https://red.ht/sig>
<https://redhat.com/summit>
On Mon, Jan 13, 2025 at 7:57 AM <jordan(a)olinsolutions.com> wrote:
In the current packstack instructions for RDO here:
https://www.rdoproject.org/deploy/packstack/ under the Network section it
states the following:
"If you plan on having external network access to the server and
instances, this is a good moment to properly configure your network
settings. A static IP address to your network card, and disabling
NetworkManager are good ideas."
But, then it shows not only disabling NetworkManager, but also enabling
the "network" service:
sudo systemctl disable firewalld;
sudo systemctl stop firewalld;
sudo systemctl disable NetworkManager;
sudo systemctl stop NetworkManager;
sudo systemctl enable network;
sudo systemctl start network
The problem is that CentOS Stream 9 no longer has or supports the
"network" service, as it has been deprecated.
Are there alternate instructions?
Or, can I configure as usual with NetworkManager and just diable it once
the configurations are working?
_______________________________________________
users mailing list -- users(a)lists.rdoproject.org
To unsubscribe send an email to users-leave(a)lists.rdoproject.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s
1:42 a.m.
New subject: Latest RDO Packstack wants "network" serivcei for external networking, but is not available in CentOS Stream 9
Thank you @brendan! That was it!!
I cannot tell you how many days I have searched and experimented to get past this (even
tried systemd-networkd to no avail).
One small thing, CentOS Stream 9 does give me the "SysV service
'/etc/rc.d/init.d/network' lacks a native systemd unit file." every time the
service is restarted. Do you know where I can find an equivalent to drop in and eliminate
that warning? It looks like it is supposed to be generating one, but that apparently does
not work.
Regardless, thank you again.
- Jordan.
4:21 a.m.
New subject: Latest RDO Packstack wants "network" serivcei for external networking, but is not available in CentOS Stream 9
Hey,
SystemD generates a drop-in file to work with these legacy init scripts, so for this
network one, it generates:
# systemctl cat network
# /run/systemd/generator.late/network.service
# Automatically generated by systemd-sysv-generator
[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/rc.d/init.d/network
Description=LSB: Bring up/down networking
Before=network-online.target
Before=network.target
After=iptables.service
After=ip6tables.service
After=NetworkManager-wait-online.service
After=NetworkManager.service
After=network-pre.target
Wants=network-online.target
Wants=network.target
[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
SuccessExitStatus=5 6
ExecStart=/etc/rc.d/init.d/network start
ExecStop=/etc/rc.d/init.d/network stop
The warning is just a symptom of the network-scripts being a legacy service that should
really be removed. So systemd generates the .service file for the legacy sysvinit script
using the sysv-generator and then warns users about it.
Nothing to worry about in your case.
Brendan Shephard
Senior Software Engineer
Red Hat Australia
On 13 Jan 2025, at 17:42, jordan(a)olinsolutions.com wrote:
Thank you @brendan! That was it!!
I cannot tell you how many days I have searched and experimented to get past this (even
tried systemd-networkd to no avail).
One small thing, CentOS Stream 9 does give me the "SysV service
'/etc/rc.d/init.d/network' lacks a native systemd unit file." every time the
service is restarted. Do you know where I can find an equivalent to drop in and eliminate
that warning? It looks like it is supposed to be generating one, but that apparently does
not work.
Regardless, thank you again.
- Jordan.
_______________________________________________
users mailing list -- users(a)lists.rdoproject.org
To unsubscribe send an email to users-leave(a)lists.rdoproject.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s
9:01 a.m.
New subject: Latest RDO Packstack wants "network" serivcei for external networking, but is not available in CentOS Stream 9
Thank you for the explanation, Brendan.
Kind regards,
Jordan.
===========================
Jordan Olin, TOGAF EA
President and Chief Solutioneer
OLINSolutions, Inc.
e: jordan(a)olinsolutions.com
p: +1 508-982-4872
w: olinsolutions.com
This email and any files transmitted with it are confidential and are intended solely for
the use of the individual or entity to which they are addressed. This communication may
contain material protected by government legislation. If you are not the intended
recipient or the person responsible for delivering this email to the intended recipient,
be advised that you have received this email in error and that any use, dissemination,
forwarding, printing or copying of this email is strictly prohibited. If you have received
this email in error, please notify the sender by replying to this email and then delete
the email from your computer.
On Jan 13, 2025, at 03:21, Brendan Shephard
<bshephar(a)redhat.com> wrote:
Hey,
SystemD generates a drop-in file to work with these legacy init scripts, so for this
network one, it generates:
# systemctl cat network
# /run/systemd/generator.late/network.service
# Automatically generated by systemd-sysv-generator
[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/rc.d/init.d/network
Description=LSB: Bring up/down networking
Before=network-online.target
Before=network.target
After=iptables.service
After=ip6tables.service
After=NetworkManager-wait-online.service
After=NetworkManager.service
After=network-pre.target
Wants=network-online.target
Wants=network.target
[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
SuccessExitStatus=5 6
ExecStart=/etc/rc.d/init.d/network start
ExecStop=/etc/rc.d/init.d/network stop
The warning is just a symptom of the network-scripts being a legacy service that should
really be removed. So systemd generates the .service file for the legacy sysvinit script
using the sysv-generator and then warns users about it.
Nothing to worry about in your case.
Brendan Shephard
Senior Software Engineer
Red Hat Australia
> On 13 Jan 2025, at 17:42, jordan(a)olinsolutions.com wrote:
>
> Thank you @brendan! That was it!!
>
> I cannot tell you how many days I have searched and experimented to get past this
(even tried systemd-networkd to no avail).
>
> One small thing, CentOS Stream 9 does give me the "SysV service
'/etc/rc.d/init.d/network' lacks a native systemd unit file." every time the
service is restarted. Do you know where I can find an equivalent to drop in and eliminate
that warning? It looks like it is supposed to be generating one, but that apparently does
not work.
>
> Regardless, thank you again.
>
> - Jordan.
> _______________________________________________
> users mailing list -- users(a)lists.rdoproject.org
> To unsubscribe send an email to users-leave(a)lists.rdoproject.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>
> To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s
21
days inactive
22
days old
4 comments
3 participants
participants (3)
-
Brendan Shephard -
Jordan Olin (OLINSolutions) -
jordan＠olinsolutions.com