Incorrect information in docs

[7331eraCkcuFetHwoD]

https://magma.github.io/magma/docs/next/lte/s1ap_tests#gateway-vm-setup

Gateway VM setup -> Debian installation step one produces no error, but also doesn't trigger any services, so step two is an empty list.

Am I not following the two steps correctly or is this deprecated, if it is the last case please remove or comment out or write deprecated in the title.

[nstng]

Hi @7331eraCkcuFetHwoD, this is working for me as expected:

vagrant@magma-deb:~/magma$ systemctl list-units --type=service magma@*
  UNIT                           LOAD   ACTIVE SUB     DESCRIPTION                   
  magma@control_proxy.service    loaded active running Magma control_proxy service   
  magma@ctraced.service          loaded active running Magma ctraced service         
  magma@directoryd.service       loaded active running Magma directoryd service      
  magma@dnsd.service             loaded active running Magma dnsd service            
  magma@enodebd.service          loaded active running Magma enodebd service         
  magma@envoy_controller.service loaded active running Magma envoy controller service
  magma@eventd.service           loaded active running Magma eventd service          
  magma@magmad.service           loaded active running Magma magmad service          
  magma@mme.service              loaded active running Magma OAI MME service         
  magma@mobilityd.service        loaded active running Magma mobilityd service       
  magma@pipelined.service        loaded active running Magma pipelined service       
  magma@policydb.service         loaded active running Magma policydb service        
  magma@redis.service            loaded active running Magma Redis datastore service 
  magma@sessiond.service         loaded active running Magma session manager service 
  magma@smsd.service             loaded active running Magma smsd service            
  magma@state.service            loaded active running Magma state service           
  magma@subscriberdb.service     loaded active running Magma subscriberdb service    

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

17 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

As this method installs the latest CI build you might have been unlucky and installed a damaged artifact. Can you try again? You can install a specific artifact by using

MAGMA_PACKAGE="magma=1.9.0-1672417642-9aa05ea4" vagrant up magma_deb

The one I used in the example had a green integration test run (see https://github.com/magma/magma/actions/runs/3807925777), i.e., I expect it to work correctly.