Features

• CFY-6300 – Bootstrap validation should ensure that ssh_user has passwordless sudo
• CFY-7077 – Script plugin – add a way to pass a cert to the `requests.get`
• CFY-7119 – enable and disable external ssl after bootstrap
• CFY-7126 – Support Okta Auth
• CFY-7129 – Add cert_path parameter to cfy profiles use
• CFY-7140 – Add certificate path parameter to profiles commands
• CFY-7211 – Add a way to use a profile for a not responding manager
• CFY-7212 – A way to teardown managers with non-responding REST service
• CFY-7223 – Improve and automate SSL commands
• CFY-7231 – Removing a node from cluster should update its profile
• STAGE-15 – responsive for menu
• STAGE-30 – widget category
• STAGE-164 – Navigate to page
• STAGE-443 – plugins catalog
• STAGE-445 – Blueprint Catalog (readme icon)
• STAGE-480 – change composer links to match composer’s new port
• STAGE-305 – Template management
• STAGE-408 – Open sourcing the UI
• COMPOSER-235 – It’s hard to drag two docker containers into one VirtualMachine
• COMPOSER-782 – Remove defaultData from being saved on the node
• COMPOSER-783 – Separate topology from angular
• COMPOSER-542 – Two way editing

Fixed Issues

• CFY-5808 – “cli” node in manager blueprint fails to create
• CFY-5832 – RPM’s end up referring to external pypi repo
• CFY-5847 – No Idempotency on snapshot recovery
• CFY-5854 – Sanity app erroneously refers to public IP
• CFY-6041 – CLI installation from manager blueprint is broken
• CFY-6580 – (Script plugin) incorrect handling of HTTP errors when downloading resources
• CFY-6760 – Snapshot restore error
• CFY-6763 – Agent installation currently mandates manager access through private IP
• CFY-6764 – Can’t create snapshot with deployment
• CFY-6803 – Operations using the REST client on Python 2.6 may fail
• CFY-6810 – Bootstrap validation should ensure python-setuptools is installed
• CFY-6813 – Wrong message when trying to use a dead manager’s profile
• CFY-6819 – Host validation is done too late
• CFY-6821 – Non-empty manager (with resources) can join cluster
• CFY-6822 – Manager can be used as stand alone manager after been removed from cluster
• CFY-6830 – Don’t show internal logs to the user
• CFY-6850 – Extra, unneeded info printed when not all inputs are provided
• CFY-6859 – Error with joining manager to cluster after removing the active manager from the cluster
• CFY-6906 – cli stays connected to the passive manager on a cluster
• CFY-6918 – Creating new tenant on snapshot restore is not validated
• CFY-6924 – Bootstrap fails when private_ip is a hostname
• CFY-6927 – Bootstrap hangs when failing validations
• CFY-6947 – Extraneous output shown when get_input usage is invalid
• CFY-6976 – Exception causes are never printed
• CFY-7000 – Workflow events monitor: only stop after it has been started
• CFY-7019 – Timeout error message in CLI while uploading plugins inside HA cluster (the upload itself works)
• CFY-7022 – There are no logs available for snapshots
• CFY-7030 – Connection error to manager outside the cluster
• CFY-7039 – No ports reachability validation on cluster start
• CFY-7048 – `cfy profiles use` can use cluster settings of the previous profile
• CFY-7050 – Current DB locking mechanism is not sufficient in edge cases
• CFY-7058 – Snapshot restore backend (rest service + workflow) still expect tenant_name
• CFY-7066 – fix_snapshot_ssh_db.py doesn’t respect passed in tenant name (overwrites matching key paths with secret ID for all tenants’ deployments)
• CFY-7067 – cfy agents install for other tenants failing
• CFY-7069 – In snapshot create only credentials from the current tenant are saved
• CFY-7078 – Windows cli packages are broken
• CFY-7080 – Save resource under folder in the tmp folder, and not directly under the tmp folder
• CFY-7081 – `cfy -vvvv` doesn’t show tracebacks
• CFY-7082 – Fabric version changes during bootstrap, causing CLI not to work
• CFY-7083 – Windows cli bootstrap is broken due to invalid path
• CFY-7084 – Fix integration test with target_aware_mock plugin
• CFY-7085 – System tests fail due to dir creation
• CFY-7086 – Agents upgrade is broken due to new config
• CFY-7087 – Userdata install is broken due to small bug in agent config
• CFY-7090 – In-place upgrade failure with SSL certificates
• CFY-7095 – restore-certificates flag failure from 3.4.2 manager snapshot to master manager
• CFY-7109 – Conflict in fabric versions between CLI and cloudify-fabric-plugin
• CFY-7110 – Uninstall failure after set-active on cluster
• CFY-7111 – snapshot restore should return error without trying to perform the action if user is not a “super-admin”
• CFY-7112 – User should not be able to perform any actions on snapshots if it’s not an admin user
• CFY-7115 – Users should not be able to perform any action regarding snapshots
• CFY-7116 – Key-pairs inside secrets store doesn’t restore on snapshot
• CFY-7120 – Agent installation with Fabric runner should run with sudo privileges
• CFY-7123 – client copy of rest certificate is in the general workdir
• CFY-7124 – Fix agent system tests
• CFY-7130 – cfy dev command doesn’t work
• CFY-7137 – Failure connecting to manager from bootstrap, after enabling ssl
• CFY-7141 – Snapshot restore fails on community due to credentials tenant lookup
• CFY-7142 – Command line too long on agent installation through winrm
• CFY-7144 – Cluster – only remove old db dir after successfully cloning the new one
• CFY-7145 – Cluster CLI restclient needs to retry requests sent to removed nodes
• CFY-7150 – User connection failure after snapshot restore
• CFY-7165 – Quick successive failovers can leave the master in half-promoted state
• CFY-7166 – restore snapshot with certificate restore replaces the whole ssl dir
• CFY-7167 – “SSL enable” fails communication between CLI and manager image
• CFY-7169 – Second CLI receives an error while trying to connect to manager with ssl enable
• CFY-7172 – Install script not removed from manager after running agent upgrade
• CFY-7173 – Unable connect to bootstrapped manager after using ssl manager
• CFY-7175 – CLI fails to connect a passive manager after set-active
• CFY-7176 – CLI fails to connect to his bootstrap manager after SSL
• CFY-7181 – Default import resolver rules should include cloudify.co
• CFY-7182 – Cluster – handlers can be skipped if value changes during retries
• CFY-7183 – Fix suites_splitter path and remove testnameextractor nose plugins
• CFY-7186 – Misleading error message if invalid YAML provided as input file
• CFY-7188 – Cluster error with SSL enabled
• CFY-7199 – New rest certificate property of CLI profile breaks on old profiles
• CFY-7213 – Cluster start: cloning database can use a non-existent directory
• CFY-7214 – cfy agents install –all-tenants not working with empty default tenant
• CFY-7218 – nginx startup verification uses internal address with external port
• CFY-7222 – Bootstrap fails on RHEL 7.4
• CFY-7237 – Cluster’s HandlerRunner might get stuck in a busy loop
• CFY-7245 – trying to get info on your own user fails in community edition
• CFY-7250 – /etc/cloudify/cluster is world-readable
• CFY-7251 – Cannot add new node to cluster after failover
• CFY-7253 – Inconsistent behaviour for 80 -> 443 redirect
• CFY-7265 – Snapshot restore certificates fails with new internal CA
• CFY-7267 – Incorrect agent connectivity details ends up in unhelpful message being created
• CFY-7271 – An unauthenticated request to Composer doesn’t redirect the user to Stage login page
• CFY-7272 – Manager IP setter doesn’t update logstash conf file
• CFY-7276 – External certificates that were created by us should be recreated by the IP setter
• CFY-7300 – create snapshot is broken
• CFY-7302 – Nginx redirect should be reinstated to all paths except the API
• CFY-7305 – Non-admin users not working after snapshot restore
• CFY-7313 – Restores to 4.1 and 4.1.1 break with 4.0.1 where SSH keys are on the filesystem
• CFY-7316 – Failed connecting to stage through Okta by bootstrapped manager
• CFY-7321 – Don’t require tenant in config api
• CFY-7323 – Update security_configuration with admin cred
• CFY-7332 – Can’t enable ssl inside cluster
• CFY-7336 – Allow stage read rest-security.conf
• CFY-7337 – expose tenants api in community
• CFY-7345 – Plugin installation – errors might not be displayed
• CFY-7354 – Snapshot restores broken by new permissions logic
• CFY-7356 – 3.4.2 -> 4.2 snapshot restore fails
• CFY-7361 – Logs should not be removed on teardown
• CFY-7365 – fix widget names in permissions conf
• CFY-7377 – Unauthorized User returns 401 instead of 403
• CFY-7379 – Fix 4.2 snapshot integration test
• CFY-7380 – fix openssl version validation
• CFY-7382 – Private resource is broken
• CFY-7383 – Cannot restore snapshots with riemann policies
• CFY-7384 – Tenant Manager has the ability of managing users
• CFY-7385 – Tenant User has the ability of managing secrets
• CFY-7386 – Tenant Viewer and Tenant Ops Mgr can access to the composer by negative to composer’s url+port
• CFY-7387 – Cluster start/join: validate –cluster-host-ip is actually ip
• CFY-7388 – Simple Manager Bootstrap SSL verification fails
• CFY-7392 – Tenant viewer can add widgets (UI)
• CFY-7393 – Tenant-Opt-Mgr Role doesn’t exist
• CFY-7395 – Cluster: lockfile permission denied with re-created user
• CFY-7409 – Failed to load blueprint on composer after set-active on manager
• CFY-7410 – Tenant Manager can’t access other’s private resources.
• CFY-7411 – Fix wagon integration test
• CFY-7412 – Fix community multi network system test
• CFY-7415 – Cluster join continues polling with the wrong credentials
• CFY-7418 – Wrong role for user after in-place upgrade
• CFY-7420 – “yum install” attempts to access yum repos
• CFY-7421 – Listing tenants fails on community manager
• CFY-7423 – Certain RPM’s missing from manager resources package
• CFY-7434 – CLI should not be uninstalled if it existed before bootstrap
• CFY-7437 – In-place upgrade crashes the stage and changes the password
• CFY-7439 – “cfy profile use” ignores existing REST protocol
• CFY-7443 – “cfy plugins upload” usually fails when using local wagon
• CFY-7444 – Can’t add logs/events filter – widget is stuck on loading
• CFY-7445 – Global plugin restored as tenant resource
• CFY-7446 – Tenant Manager has the ability to list user-group
• CFY-7455 – Certain Wagons cannot be uploaded
• CFY-7457 – Unable to delete tenants and user groups with specific names
• CFY-7459 – Missing requirements in docl
• CFY-7461 – Invalid certificate error with any CFY CLI command
• CFY-7483 – Snapshot failure with modified home directory
• CFY-7490 – global resources should not require tenant for authorization
• CFY-7500 – `cfy cluster join` uses incorrect CA key to generate certs
• CFY-7503 – Snapshot restore fails on bootstrapped managers
• CFY-7504 – Composer can’t edit blueprints restored from a snapshot
• CFY-7505 – no stage in HA mode
• CFY-7506 – Snapshot does not contain composer DB
• CFY-7508 – ‘Stage’ service on auto-restart mode after set-active on cluster
• CFY-7509 – inplace upgrade from 4.1.1 is broken
• CFY-7537 – Fail to uninstall blueprint from second manager in cluster
• CFY-7551 – Failed to login the UI after start cluster and restore snapshot
• CFY-7552 – 4.1.1 -> 4.2 restore breaks stage
• CFY-7564 – Cannot upgrade a cluster
• CFY-7565 – Requests without tenants are handled incorrectly
• CFY-7571 – Bootstrap fails during in-place upgrade process after manager teardown in HA cluster
• CFY-7579 – Add setup tools version requirement to agent dev-requiremets
• STAGE-272 – Numeric deployment inputs sent as a string
• STAGE-274 – Logs are not in /var/log
• STAGE-275 – User with no tenant can log in ?
• STAGE-276 – Deleting deployment/blueprint on drilldown page
• STAGE-320 – Usability: Login screen should focus on the username field
• STAGE-324 – Number of node instances is not shown in deployment page
• STAGE-330 – When adding a “graph” widget to a new page I’ve created, the screen freezes.
• STAGE-335 – Axis and ticks are not formatted properly for graphs
• STAGE-378 – “Cannot parse upload response” Error when uploading a blueprint
• STAGE-381 – Error message shown in the UI won’t disappear and just keep appearing until the page refreshed
• STAGE-382 – When opening a list in any of the widgets configurations, if scrolling without closing the list first, it stays open infront of everything else in that modal
• STAGE-383 – Blueprints widget configuration label error
• STAGE-386 – Events and logs with long message
• STAGE-389 – When user is not assigned to a tenant instead of getting an error message, he gets white scren
• STAGE-390 – On deploying topology, when in status starting, the icon is wrong
• STAGE-391 – Events and logs type vs icon
• STAGE-412 – Error messages in popups disappear after 5 sec
• STAGE-414 – Node statistics widget keeps reloading
• STAGE-421 – Adjust ‘loading’ spinner in widget header to allow access to widget config while data is loading
• STAGE-427 – Focus jumps to the top of the screen after changing widgets that are at the bottom of the page.
• STAGE-434 – Plugin ID isn’t a link, so it shouldn’t look like it is 🙂
• STAGE-438 – Finding list of blueprints files when uploading a blueprint stopped working
• STAGE-442 – stage is not recoverable with token only
• STAGE-459 – fix using (initial template) instead of (initial template admin)
• STAGE-464 – Execute workflow “uninstall” improvements.
• STAGE-466 – Widgets names in catalog shouldn’t be links
• STAGE-486 – Force switch is not working in execution deployment modal
• STAGE-487 – DB migration and enum issue
• STAGE-492 – Optimize InputTimeFilter component
• STAGE-499 – Wrong redirection from okta to stage if user isn’t associated to tenant
• STAGE-500 – no error when stage failed to initialize with okta
• STAGE-501 – Snapshot name in the snapshots widgets shouldn’t appear as a link
• STAGE-509 – Remove consts.ROLE_ADMIN/ROLE_USER
• STAGE-516 – Events Filter widget render method error
• STAGE-517 – Multi-charting broken when the same metric is selected more than once
• STAGE-518 – Stage fails to read rest security file on permission error
• STAGE-520 – Invalid placement and width of Time Filter popup
• STAGE-521 – Some responses from manager REST API are not parsed properly
• STAGE-563 – …And now Templates do not apply for any user other than Admin
• COMPOSER-147 – Module name is missing in some cases when adding a plugin by zip / zip url
• COMPOSER-374 – clicking on delete inputs not always opens the confirm popover
• COMPOSER-375 – Unable to clear ‘type’ selection in inputs
• COMPOSER-378 – intrinsic functions autocomplete doesn’t work mid writing
• COMPOSER-534 – Able to add the same import more than once
• COMPOSER-622 – Value and type fields of a new property in a new custom type have a weird behaviour
• COMPOSER-669 – We should add validation check before importing a BP to a manager
• COMPOSER-746 – Getting an undetailed “error” message alongside a success message when importing the attached blueprint
• COMPOSER-748 – If the input name is to long, it exceeds the textbox
• COMPOSER-749 – long values in inputs default field are shown in partial – only their ending (the text is being cut to rows and only the last one is shown)
• COMPOSER-752 – When importing a BP and giving it a name of an existing BP, getting an uninformative error message
• COMPOSER-754 – Can’t choose a group after it was created (so I can’t delete/edit it)
• COMPOSER-774 – Getting an error when trying to add a resource file under a folder
• COMPOSER-781 – Can’t remove “types.yaml” from imports
• COMPOSER-787 – Remove defaultData being saved on the customTypes
• COMPOSER-796 – When trying to change a name of a resources folder the second time, the screen gets stuck in “processing” mode
• COMPOSER-805 – Composer fails to load if there is a ‘stuck’ user in session
• COMPOSER-809 – Blueprint deletion weird behavior
• COMPOSER-811 – Read all gets too much data
• COMPOSER-813 – Outputs complex values not working properly
• COMPOSER-815 – When switching blueprints, description remains of the old one
• COMPOSER-816 – Blueprint description is not being saved.
• COMPOSER-821 – After I remove the types.yaml file from import, it can’t be added again
• COMPOSER-829 – context root not fully working
• COMPOSER-832 – composer loading without token loads app then redirect
• COMPOSER-835 – Unable to add inputs without type in composer
• COMPOSER-838 – Interface input edit- if input type is boolean shouldnt show property editor
• COMPOSER-840 – Allows removing a custom type & custom relationships type for used nodes when node type updates
• COMPOSER-842 – Fetch topology rules when pages loads (after user logged in)
• COMPOSER-843 – Fetch oob imports when pages loads (after user logs in)
• COMPOSER-844 – Plugins in resources bad behavior
• COMPOSER-848 – The error we get during importing an archive, when not specifying the main blueprint file name, and there is no file with the default name blueprint.yaml in the folder, is not optimal
• COMPOSER-859 – Node_templates value: None’ while trying to copy Blueprint example’s source code.
• COMPOSER-860 – Error while trying to delete blueprint.
• COMPOSER-865 – Can’t connect Router and Load Balancer component to any other components.
• COMPOSER-867 – When I create an invalid source and choose “save”, the data disappears and composer get stuck on loading
• COMPOSER-868 – Composer automatically creates a “relationship” section
• COMPOSER-869 – Download doesn’t work
• COMPOSER-888 – Wrong text on the button of upload blueprint
• COMPOSER-889 – Wrong zip name when downloading a blueprint
• COMPOSER-891 – DSL parser is not updated