Member since 
    
	
		
		
		11-09-2017
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                69
            
            
                Posts
            
        
                17
            
            
                Kudos Received
            
        
                13
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 1506 | 04-05-2019 08:50 AM | |
| 1274 | 04-04-2019 05:17 PM | |
| 2035 | 04-04-2019 05:08 PM | |
| 1925 | 09-11-2018 09:12 AM | |
| 3075 | 06-27-2018 03:11 PM | 
			
    
	
		
		
		06-27-2018
	
		
		03:11 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @Jakub Igla,  it looks like your virtual machines haven't got an hostname/domain name. This can be a DHCP or (reverse) DNS issue. Could you post the output of the following commands:  hostname -d
hostname -f  Also please attach the following:   /var/log/saltboot.log  /var/log/dhcp-hook.log (if present)  output of: "journalctl -t dhcp-hook" (if previous is missing)  
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-27-2018
	
		
		02:56 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @Jakub Igla,  we are aware of this issue and have the fix for it, but we don't have the release date for 2.7.1  Until we release 2.7.1, if this issue is blocking, you can switch to cloudbreak rc version which has the fix. To use the it add the following line to your Profile under deployment directory and use 'cbd restart' to activate the changes (this will restart Cloudbreak):  export DOCKER_TAG_CLOUDBREAK=2.7.1-rc.13  Please be aware that's not a released version, and use at your own risk. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-27-2018
	
		
		02:48 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 
	Hi @Mai Nakagawa,  
	yes, it's a bug in 2.7.0 but we managed to create the fix, but we are not ready yet to release 2.7.1  
	If you would like to use the fix, please update the DOCKER_TAG_PERISCOPE variable to 2.7.1-rc.13 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-27-2018
	
		
		09:20 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @NaveenKrishna Murakonda,  Only 80,443 ports are necessary to be open. In your Profile file you should set the PUBLIC_IP and PRIVATE_IP variable according to your instance IP addresses and issue 'cbd restart' to take effect. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-26-2018
	
		
		03:00 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @Mai Nakagawa,  I could not find the cause of you issue in the logs, but I have a build which have the logging issue solved hopefully. If it is a test environment you have, you can check out the new periscope to see the real error.  To have the new version please add the following line to you Profile under deployment directory:  export DOCKER_TAG_PERISCOPE=2.7.1-rc.11  And after it you have to issue the   cbd restart  command. This will terminate cloudbreak, regenerate the docker-compose.yml with the new version of periscope, then start cloudbreak again. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-26-2018
	
		
		12:50 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @JJ,  If you do that, then Cloudbreak won't know about that node. Maybe it will work, but it's not supported. In my opinion the best way to fix this is to recreate the cluster with the correct setup. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-26-2018
	
		
		12:31 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @JJ,  What you attached is the cluster creation json, not the blueprint. If you click the blueprint name in the "Cluster information" part of the UI, it will navigate you to it.  Anyway, from your attached json it seems to me that your edge hostgroup called "cot-edge01-env01-hosts" is GATEWAY type, so it's not possible to scale it up. Have you selected this hostgroup to have tha Ambari server? To fix this you have to recreate your cluster and select another group to have your Ambari server. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-26-2018
	
		
		11:29 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @JJ,  On the UI we do not enable the resize button for hostgroup which type is GATEWAY or GATEWAY_PRIMARY. You can check this under the actions -> Show CLI command and look at the instanceGroups part of the json.  When you try to scale we check several things, and it includes the Cardinality in the Blueprint. So if you would like to scale edge hostgroup it should have 1+ cardinality. We also check the services cardinality based on this:   https://github.com/hortonworks/cloudbreak/blob/rc-2.7/blueprint-manager/src/main/resources/hdp/hdp-services.json  For further investigation we would need your blueprint so we could test your scenario. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-26-2018
	
		
		09:09 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @Mai Nakagawa,  It looks like we have some logging issue here, so I can't see the real reason. Could you attach please the Cloudbreak  log file from the same time? You can find the file under your deployment directory in the logs subfolder.  In the meanwhile we will work on fixing the logging issue.  Thanks 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-26-2018
	
		
		08:00 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @NaveenKrishna Murakonda,  I think you should try to set a registry mirror for your docker daemon:   https://docs.docker.com/registry/recipes/mirror/  Other option is to override the default docker image name's generated by cbd by editing your Profile file. To show all the environmant option you can use  cbd env show  The relevant environment variables for you (and also you can find the TAG ones to further customize):  DOCKER_IMAGE_CLOUDBREAK  = Cloudbreak Docker image name [hortonworks/cloudbreak]  DOCKER_IMAGE_CLOUDBREAK_WEB  = Web UI Docker image name [hortonworks/hdc-web]  DOCKER_IMAGE_CLOUDBREAK_AUTH  = Authentication service Docker image name [hortonworks/hdc-auth]  DOCKER_IMAGE_CLOUDBREAK_PERISCOPE  = Autoscale Docker image name [hortonworks/cloudbreak-autoscale]  DOCKER_IMAGE_CBD_SMARTSENSE  = SmartSense Docker image name [hortonworks/cbd-smartsense]  I hope one of this can solve your issue. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		- « Previous
- 
						- 1
- 2
 
- Next »
 
         
					
				













