Waiting for FRR service

[avallk]

Trying to install holorouter and am stuck Waiting for FRR service.
Have run the install twice... the first time the Waiting for FRR service looped for over 5 hours before killing the process. Ran a second time and the log file looks like:
18-10-2025 00:41:17  Auth[18225]: [INFO] Testing connectivity to Target Host
18-10-2025 00:41:18  Auth[18225]: [SUCCESS] 10.16.210.209 is successfully connected!
18-10-2025 00:41:18  Auth[18225]: [INFO] Target host is a vCenter
18-10-2025 00:41:18  SetHoloDeckConfig[18225]: [INFO] Updating the Global Config, ConfigKey: TargetHostApiType, ConfigValue: VirtualCenter
18-10-2025 00:41:18  HoloDeck[18225]: [INFO] Log level set to: INFO
18-10-2025 00:41:18  HoloDeck[18225]: [INFO] The runtime Environment is Unix, Setting up the HoloDeck Root Folder to /holodeck-runtime
18-10-2025 00:41:19  SetHoloDeckConfig[18225]: [INFO] Updating the Global Config, ConfigKey: rootFolderPath, ConfigValue: /holodeck-runtime
18-10-2025 00:41:19  HoloDeck[18225]: [INFO] Welcome to HoloDeck 9.0!
18-10-2025 00:41:19  HoloDeck[18225]: [INFO] Retrying execution, using the same output.txt file
18-10-2025 00:41:39  SetHoloDeckConfig[18225]: [INFO] Updating the Global Config, ConfigKey: InstanceID, ConfigValue: demo
18-10-2025 00:41:39  HoloDeck[18225]: [INFO] Validating the LabStorage/HoloDeckISO Path
18-10-2025 00:41:43  HoloDeck[18225]: [SUCCESS] HoloDeckISO Folder on LabStorage exists
18-10-2025 00:41:47  HoloDeck[18225]: [DEBUG] Start Push-HoloDeckState Function
18-10-2025 00:41:47  SetHoloDeckState[18225]: [DEBUG] after function completion:
18-10-2025 00:41:47  SetHoloDeckState[18225]: [DEBUG] New-HoloDeckInstance
18-10-2025 00:41:47  SetHoloDeckConfig[18225]: [INFO] Updating the Global Config, ConfigKey: vSANMode, ConfigValue: ESA
18-10-2025 00:41:47  HoloDeck[18225]: [DEBUG] Start Push-HoloDeckState Function
18-10-2025 00:41:47  SetHoloDeckState[18225]: [DEBUG] after function completion:
18-10-2025 00:41:47  SetHoloDeckState[18225]: [DEBUG] New-HoloDeckInstance SingleSite
18-10-2025 00:41:47  HoloDeck[18225]: [DEBUG] Start Push-HoloDeckState Function
18-10-2025 00:41:47  SetHoloDeckState[18225]: [DEBUG] after function completion:
18-10-2025 00:41:47  SetHoloDeckState[18225]: [DEBUG] New-HoloDeckInstance SingleSite FullStack
18-10-2025 00:41:47  HoloDeck[18225]: [INFO] Creating Single Site HoloDeck Instance with VCF Management & Workload Domain Only with default configurations!
18-10-2025 00:41:49  Network-Manager-Init[18225]: [SUCCESS] Network Configuration Generated Successfully
18-10-2025 00:41:49  HoloRouter-Setup[18225]: [DEBUG] Start Push-HoloDeckState Function
18-10-2025 00:41:49  SetHoloDeckState[18225]: [DEBUG] after function completion:
18-10-2025 00:41:49  SetHoloDeckState[18225]: [DEBUG] New-HoloDeckInstance SingleSite FullStack Set-HoloRouter
18-10-2025 00:41:49  HoloRouter-Setup[18225]: [INFO] Configuring startup file
18-10-2025 00:41:50  HoloRouter-Setup[18225]: [INFO] Configuring service configuration files
18-10-2025 00:41:51  HoloRouter-Setup[18225]: [INFO] Configuring iptables
18-10-2025 00:41:51  HoloRouter-Setup[18225]: [DEBUG] Start Push-HoloDeckState Function
18-10-2025 00:41:51  SetHoloDeckState[18225]: [DEBUG] after function completion:
18-10-2025 00:41:51  SetHoloDeckState[18225]: [DEBUG] New-HoloDeckInstance SingleSite FullStack Set-HoloRouter Install-FRR
18-10-2025 00:41:51  HoloRouter-Setup[18225]: [INFO] Installing BGP Router
18-10-2025 00:41:51  HoloRouter-Setup[18225]: [INFO] Waiting for FRR service
18-10-2025 00:42:01  HoloRouter-Setup[18225]: [INFO] Waiting for FRR service
18-10-2025 00:42:11  HoloRouter-Setup[18225]: [INFO] Waiting for FRR service
18-10-2025 00:42:21  HoloRouter-Setup[18225]: [INFO] Waiting for FRR service
18-10-2025 00:42:31  HoloRouter-Setup[18225]: [INFO] Waiting for FRR service
18-10-2025 00:42:41  HoloRouter-Setup[18225]: [INFO] Waiting for FRR service
-----------
$error | out-file error.txt results with:

New-Item: The file '/holodeck-runtime/output/network_manager_config_site_a.yaml' already exists.

Get-Item: Cannot find path '/holodeck-runtime/output/output.txt' because it does not exist.

-------------------------------------------

[Amith Balakrishnan]

I'm facing the same issue. Were you able to find a solution?

-------------------------------------------

[avallk]

No. I found no solution. And got no feed back. I roasted the setup environment.

[Amith Balakrishnan]

I ran out of patience and redeployed the Holorouter, and that helped me move past the stuck message. I did miss the chance to figure out what caused the issue in the first place, though.

-------------------------------------------

[Nikhil M Kulkarni]

@avallk and @Amith Balakrishnan are you facing this issue with Holorouter 9.0 or Holorouter 9.0.1?

-------------------------------------------

[Amith Balakrishnan]

It's Holodeck 9.0.1

-------------------------------------------

[avallk]

Same.. 9.0.1

[Jim Jones]

Has anybody ever got to the root of this? I'm currently running into it as well. Trying to deploy 9.0.1.0 to a v8 environment. I've rebuilt the holorouter I think fixing some of my networking setup; didn't realize there should be 4 PGs total in play here (unless I'm wrong):

1. mgmt NIC with IP
2. general purpose trunk for NICs 2 and 3 (holoTRUNK)
3. vSwitch0 holo-PG-A (no uplink)
4. vSwitch1 holo-PG-B (no uplink)

When I list pods I see 2 that are in create container error mode

Any ideas on where to go from here?

-------------------------------------------

[Jim Jones]

Has anybody managed to get to the root of this yet? I'm currently running into the same issue using 9.0.1.0 deploying to a pristine vSphere 8 environment. I've redeployed my networking as well as the holorouter with no avail. Networking setup (which I'm thinking is the issue) looks like this:

1. Mgmt NIC with IP (vDS)
2. holoTRUNK (trunked VLAN, vDS) assigned to NICs 2 and 3
3. vSwitch0 holo-PG-A (vSS, no uplink)
4. vSwitch1 holo-PG-B (vSS, no uplink)

When I pull the list of pods in kubectl 2 of the containers are in CreateConfigError state which I'm assuming is the issue. Has anybody seen this or have an idea of next steps?

-------------------------------------------