Reverting transactions on contract instance created inside a contract

Description

When trying to create a new contract instance within a transaction function the created contract is not always reachable.

When trying to call the following set of functions:

To create a new contract instance and store the address within the contract.

To manipulate the new contract instance by calling a function within it

The transaction reverts when calling the second functio.

Subsequentially using the below function does return the contract address, but returns empty values for the storeddata points.

This functionality should work on the EVM and shows to be working using a Parity Client.

It is impossible to create a new contract instance in a transaction and later use this created instance in a new function. It is however possible to create the contract instance on the initial deployment of the contract that creates the instance, this is however not sufficient for my solution.

Setup:
Using the latest pantheon version running inside a docker container
Running a dev chain setup, using the chain-spec file in the github (dev config), only adding a new account to the chain spec.
The following TOML was used:

Environment

None

Status

Assignee

Danno Ferrin

Reporter

Wietze Slagman

Labels

Scrum Team

Chupacabra

Refinement State

Not Started

Sprint

None

Priority

P3
Configure