Skip to content
This repository has been archived by the owner on Jul 17, 2024. It is now read-only.

could not find type std::AgentConfig in namespace std #4

Closed
ghost opened this issue Jun 30, 2017 · 5 comments
Closed

could not find type std::AgentConfig in namespace std #4

ghost opened this issue Jun 30, 2017 · 5 comments

Comments

@ghost
Copy link

ghost commented Jun 30, 2017

When using the latest version of the openstack module (or any 2.2.X version), I got this error when exporting:

[root@inmanta openstack-test]# inmanta -vvv export
INFO     Creating new virtual environment in ./.env
DEBUG    Starting compile
INFO     verifying project
WARNING  Empty deployment model.
could not find type std::AgentConfig in namespace std (reported in Construct(std::AgentConfig) (/tmp/tmpmqtlmkgr/openstack/model/_init.cf:42))

Shouldn't the compiler version be raised to 2017.2 like in the std module?
compiler_version: 2017.2

@bartv
Copy link
Contributor

bartv commented Jun 30, 2017

The latest openstack versions use this from std. The problem is that the std module contains features that require a newer compiler. Hence, the error. We are getting close to a new release so you could try to upgrade to the latest dev version:

https://pkg.inmanta.com/inmanta-oss-dev/

@ghost
Copy link
Author

ghost commented Jun 30, 2017

Sure. I'm gonna try and install the dev version.
Nevertheless, shouldn't it be safer to enforce the new version of the compiler in module.yml in order to avoid those kind of cross dependencies' issues?

@bartv
Copy link
Contributor

bartv commented Jun 30, 2017

The problem with this issue is that it is not the openstack module that requires a newer compiler. We should rethink the way we release new module versions.

I added an issue to the main compiler to change the way we release new module versions. inmanta/inmanta#442

@bartv
Copy link
Contributor

bartv commented Jul 5, 2017

This was fixed in version 2.3.3 (just released)

@bartv bartv closed this as completed Jul 5, 2017
@bartv
Copy link
Contributor

bartv commented Jul 5, 2017

My previous comment was for an other issue. However, the issue causing this should be handled in the core with an improved branching model.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant