v1.7.x error: "assertion failure with message: system contract must first be initialized"

[lpx1988]

I was Building a new private chain with EOS v1.7.1.
After create the system account (eosio.bpay, eosio.msig,... , eosio.ram, eosio.ramfee, eosio.vpay) and set system contract (eosio.token, eosio.msig), I create and issue a Token (SYS) to eosio, but when i create a ordinary account (cleos system newaccount --transfer eosio aaabbbcccddd EOS6HZEJJ8VgUEj1TKb6sVLz3pcmiHrEyCvZx9bKQpdqksDR3LoVJ --stake-net "10.0000 SYS" --stake-cpu "10.0000 SYS" --buy-ram "10.0000 SYS"), it will fail and print "assertion failure with message: system contract must first be initialized".
when i used EOS v1.6.3, it will succeed.Is this a bug in v1.7.x(v1.7.0 and v1.7.1)?

[taokayan]

please run ./cleos push action eosio init '[0,"4,SYS"]' -p eosio@active after installing the system contract.

[jgiszczak]

It is not a bug, and is not specific to v1.7.x. It's a feature that's specific to the version of eosio.system you are using. Please link to the documentation you were following that doesn't include the init step.

[lpx1988]

Got it, thanks @taokayan @jgiszczak