-
Bug
-
Resolution: Done
-
Medium
-
Guilin Release
-
None
-
None
looks like the 'offline' bootstrap is not working.
bootstrap blueprints are looking for 4.5.5/types.yaml
in cloudify manager pod or if not there, via public internet resources
cloudify manager contains 5.1.0.dev1/types.yaml.
[root@dev-dcae-cloudify-manager-54dbc95f5b-qmjrg cloudify]# ls -al
total 12
drwxr-xr-x 3 cfyuser cfyuser 4096 Oct 2 15:12 .
drwxr-xr-x 3 cfyuser cfyuser 4096 Mar 4 2020 ..
lrwxrwxrwx 1 root root 47 Oct 2 15:12 4.5.5 -> /opt/manager/resources/spec/cloudify/5.1.0.dev1
drwxr-xr-x 2 cfyuser cfyuser 4096 Oct 2 15:11 5.1.0.dev1
If cloudify manager does not have internet connectivity, it is not able to load types from internet.
WA: see above: create link in cloudify manager
If you need a separate bug report, please let me know.
Permalink
jackl added a comment - 2 days ago - edited
demskeq8 Please create a separate bug report. It's a different problem. We'll need to have the bootstrap image's Docker build process download the 4.5.5 types file and store it onto the image's file system. (We missed this when we changed the base image for the container to a newer version of Cloudify Manager.)
You can assign it to me.
Permalink
jackl added a comment - 2 days ago
Actually, it's the cm-container image Docker build that needs to change (not the bootstrap image).