I used Puppet's mySQL module to bring it up like this.

The workstation ip is 172.16.1.49 and JIRA(mySQL) VM is 172.16.1.47 (Puppet Master is 172.16.1.80);

I'm trying to access mySQL server using workbench mySQL client tool from workstation 172.16.1.49 (hence @172.16.1.49 in the grant).

Usually I know I can remotely access if I can view htp:/172.16.1.47:3306 on the browser.
On mySQL VM, if I do htp:/localhost:3306, I see some messages that means I can access the mySQL server. But htp:/172.16.1.47:3306 on itself doesn't work either.

Where the heck in my Puppet for mySQL code, did I mess up? I think somewhere in my puppet code, I am not allowing mySQL server to allow remote access.

class { '::mysql::server':
root_password => 'secret',
remove_default_accounts => true,
override_options => $override_options
}


::mysql::db { 'mydb':
user => 'jira',
password => 'secret',
dbname => 'jiraDB',
host => 'localhost',

}

mysql_grant { 'jira@localhost/*.*':
ensure => 'present',
options => ['GRANT'],
privileges => ['ALL'],
table => '*.*',
user => 'jira@localhost' ,
}


mysql_grant { 'jira@172.16.1.49/*.*':
ensure => 'present',
options => ['GRANT'],
privileges => ['ALL'],
table => '*.*',
user => 'jira@172.16.1.49' ,
}

mysql_grant { 'root@172.16.1.49/*.*':
ensure => 'present',
options => ['GRANT'],
privileges => ['ALL'],
table => '*.*',
user => 'root@172.16.1.49' ,
}

Depending on the distro you use you might only have mysql listen on lo interface and not on eth0 or similar. Debian used to have skip_network option enabled and later switch that to listen 127.0.0.1. As you can connect on the mysql machine using localhost but not the outward facing ip address I would first check the listen status of mysql.
Take a look at the error message of workbench. Guess it say not connected instead of access denied or wrong username/password.